[Savannah-dev] Re: Savannah development at CERN (+please introduce version tagging)

[Mathieu Roy]

Hi Derek,


Derek FEICHTINGER <address@hidden> a tapoté :

> sorry, Mathieu. We were not aware that this information had not been passed 
> on 
> to you. We had talked this over with Jaime in Febuary and we had thought that 
> he had communicated it to you (we even had defined a list of items and data 
> base additions and Jaime set up an agreement).
> 
> Jaime also told us, that we would be sent forms, in which we should declare 
> in 
> written form to put all our extensions under the GPL before giving us access 
> to your CVS. We have been waiting for these documents since Febuary 
> (shouldn't it be enough for me to put the usual GPL header in my code in 
> order to place it under this license? Did all of you have to sign up in this 
> way to contribute code?). 

Usually not. I did not. But usually my work on Savannah is
volunteering - maybe it's related to the fact the CERN employs you and 
may considers to be the copyright owner of the code you produce

Jaime?

> We would very much have liked to directly commit our stuff. It's a
> pity, because now Frederik and I will be moving on to other projects
> (we had not been hired for this) while another colleague will take
> over the CERN Savannah installation. But as I said, we would very
> much like to commit our stuff back.

I think that nobody will object (and I do not think that someone may
have good reason to object).

I hope that Jaime is not too busy to get a reply from him soon.


> The tagging (and maybe also the creation of development branches)
> might be a good thing, because one may not want to include
> experimental stuff in the active version, and as I understand it,
> your active version is currently synchronized from the CVS
> head.
> With a development branch departing from the production version
> tagged main branch you can easily commit bug fixes to the production
> branch, while having a separate area for development efforts (this
> is how we usually organize our projects).
> This way you, the GNU server administrators, have full control over
> which things really make it into your active version without us
> other developers endangering the functionality of your service (what
> works for us on our RedHat 7.3 based installations may not work on
> debian).

Totally agree.

 
> >         We would like to have a clean database before adding new
> >         fields, and we know that new fields would be required (propose
> >         us which one you want).
> 
> Thanks for the offer (actually our suggestions also had been in the draft 
> that 
> we prepared with Jaime. It seems to have been lost). After the feedback of 
> the last few months from our users we even have further additions. Maybe it's 
> best to post them here on the mailing list, so everybody can put forth his 
> ideas. We will prepare a list of our suggestions together with explanations.

Good.



So next step:
        - Jaime statement about the legal possibility for to you
        directly contribute on Savannah
        - Adding your savannah accounts to the Savannah project  
        - Tagging the CVS appropriately

Later:
        - come up with a list of table/fields used in the database.
        Which ones to be added, which ones to be removed
        - discuss it here
        - do the work



Aside from that my personal plans:
        - finish the split of sv_cvs in sv_users and sv_groups, easily 
        customizable with sv_update_conf
        (or `emacs|vi|whatever /etc/savannah/savannah.conf.pl`, at
        anybody option)
        - finish the new password lost procedure: crypted by gnupg if
        the user entered a key.


Regards,

          


-- 
Mathieu Roy
 
  Homepage:
    http://yeupou.coleumes.org
  Not a native english speaker: 
    http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english