Re: [H-source-users] Deciding what to do with the server side code

[Yuchen Pei]

bill-auger <bill-auger@peers.community> writes:

> ok, i re-read some of the previous discussions
>
> the easygiant developer (antonio) stated very clearly that he
> still works on it and that it is already PHP7-compatible
> and that he is totally wiling to guide the upgrade 
>
> https://lists.nongnu.org/archive/html/h-source-users/2019-03/msg00001.html
> > The development of h-sourse is maybe not active but I'm still
> > developing the framework easygiant hsource is based on, that is
> > published on sourceforge.
>
> https://lists.nongnu.org/archive/html/h-source-users/2019-03/msg00003.html
> > Hi, the website is dead, but I still push code to svn at
> > sourceforge. 
> >
> > It's designed for every kind of website or admin area. Now it 
> > is
> > also php7 compatible. I use it for my daily work as freelance
> > developer. It can now use pdo.
> >
> > A good thing would be to use the new easygiant library inside
> > h-source. If someone would like to do it, I can help with
> > instructions if some problems arise.

This is good, thanks for digging it out. My next step is to see if 
I can get the php7 compatible version to work on the staging 
server.

> regarding the state of the running code vs the published code,
> according to the admin (Ian), there should see a large
> difference - Ian suggested publishing the running code
> separately for that reason - perhaps it was done at some later
> time, but Ian did not mention doing so - i still think we should
> not presume that they are in sync, and get the actual code
> running on the server
>
> https://lists.nongnu.org/archive/html/h-source-users/2019-03/msg00012.html
> > The main issue is that h-node and h-source are quite far out of
> > sync. When I first started contributing, h-node had changes 
> > that
> > weren't on h-source, and h-source had had major changes to the
> > framework that weren't on h-node. I spent some time trying to
> > bring the two back into sync, but wasn't comfortable uploading
> > major changes to h-node which were not simply updates to what
> > was on h-node, and that I hadn't written and didn't understand.
> >
> > I've been considering simply uploading the h-node version to
> > h-source so that anyone wanting to test and contribute at least
> > has the actual version running on h-node as a good base to 
> > start
> > from. Any objections to this suggestion? It will roll back a 
> > lot
> > of the framework changes from h-source, but once this is done,
> > someone with the time can look at working with Antonio to
> > integrate the latest EasyGiant framework. Getting things 
> > running
> > smoothly on PHP7.x is long overdue.

I was given permission to take out the source from the server, so 
was able to do a more thorough diff today. Turned out I was wrong: 
there is indeed a large amount of diff, espcially in /Library. The 
diff I performed yesterday was more manual, by checking the code 
on the server against latest commits in the repo. And it fooled me 
into thinking the code was mostly in sync.

I am not convinced it is necessary to publish the server code. It 
looks like Ian's reasoning does not apply to the current 
situation, where we have a staging server to experiment any kind 
of code on, before switching the prod to the new code.

Best,
Yuchen

--
PGP Key: 47F9 D050 1E11 8879 9040  4941 2126 7E93 EF86 DFD0

signature.asc
Description: PGP signature