h-source-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [H-source-users] Potential volunteer for h-node


From: Ian Gilfillan
Subject: Re: [H-source-users] Potential volunteer for h-node
Date: Thu, 31 Dec 2015 03:13:27 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0

On 31/12/2015 01:36, Luis A. Guzman Garcia wrote:
> El mié, 23-12-2015 a las 02:15 +0200, Ian Gilfillan escribió:
>> On 10/12/2015 21:09, Luis A. Guzman Garcia wrote:
>>> For adding new vendors the required access is still being authorized by
>>> the Sysadmins.
>>> We'd love to have new hardware on the database so i think it won't be
>>> too long before we can work that out.
>> Has there been any progress on this? The code on h-node is well behind
>> the code on h-source, which has fixed a number of issues, so if this
>> last blockage can be sorted out, so that people can see their changes in
>> action on h-node, we may see a lot more activity.
>>
> Yeah. I think that would help much, maybe we can stick first to the
> important things that are outdated or typos on the site.
>
> There might be some issues still open the svn repository, otherwise i
> think that Antonio would have pushed the changes way back in time, so
> testing is required before pushing changes, and see what issues are
> still open for a live site such as h-node.
>
> Ian, i see that you're already on the savannah project, maybe we could
> start working changes there. I wanna work with language system, there
> are some users trying to set new languages and the current system is not
> really very scalable.
>
Lisa Maginnis, the FSF system administrator, got in touch today, and has
said she will grant shell access to h-node.org to both Luis and myself.
Once this has been done, I want to focus on updating h-node and
permissions for others to help with issue tracking etc.

I've got no idea what to expect - the h-node website states that it uses
SVN-387 (which is over three years old). There have been updates since
then, so this can't strictly-speaking be correct. If the website is
actually based on SVN-387  but has had other changes pushed separately,
that's going to make things interesting to sort out.

It also makes sense to start tagging releases on Savannah. At the moment
there are just hundreds of commits to trunk, with no branches, and no
releases tagged.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]