Improving the GNOME experience : request for help

Hi everyone,

You probably know that Ekiga's development is progressing at
a good
pace. 

However, maintaining the project asks much time, and coding
asks even
more time, so I would like to request help for one specific
task :

1) Prepare tarballs in case of release : ie Ekiga, OPAL and
PWLIB
tarballs
2) Test them (do at least minimal tests)
3) Upload to GNOME.org
4) Mail packagers
5) Build a repository

Also, regularly, that person should upload the required OPAL
and PWLIB
dependancies for the SVN version to GNOME.org.

Who can handle that ?

Thank you,
-- 
 _     Damien Sandras
(o-      
//    Ekiga Softphone : http://www.ekiga.org/
v_/_   NOVACOM         : http://www.novacom.be/
       FOSDEM          : http://www.fosdem.org/
       SIP Phone       : sip:dsandrasekiga.net
                       

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

All,

On 6/7/07, Damien Sandras <dsandrasseconix.com> wrote:

> However, maintaining the project asks much time, and
coding asks even
> more time, so I would like to request help for one
specific task :
>
> 1) Prepare tarballs in case of release : ie Ekiga, OPAL
and PWLIB
> tarballs

Do you mean a release to gnome.org?   How often does this
occur?

Are releases to gnome.org after each release on ekiga.org,
or simultaneous?

> 2) Test them (do at least minimal tests)

Is a test on garnome on an x86 laptop sufficient?  If not,
does gnome
have a build-test farm?

> 3) Upload to GNOME.org
> 4) Mail packagers
> 5) Build a repository

What are the issues with the existing repositories?

> Also, regularly, that person should upload the required
OPAL and PWLIB
> dependancies for the SVN version to GNOME.org.

How often is regularly?

Can these tasks can be done by someone who is not a C
programmer?  (I
think familiarity with configuring the dependencies,
building, tarring
and using SVN, and simple scripting, is needed.)

David
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Le jeudi 07 juin 2007 à 09:43 +0100, David Corking a écrit
:
> All,
> 
> On 6/7/07, Damien Sandras <dsandrasseconix.com> wrote:
> 
> > However, maintaining the project asks much time,
and coding asks even
> > more time, so I would like to request help for one
specific task :
> >
> > 1) Prepare tarballs in case of release : ie Ekiga,
OPAL and PWLIB
> > tarballs
> 
> Do you mean a release to gnome.org?   How often does
this occur?
> 

Every time we do a release.

> Are releases to gnome.org after each release on
ekiga.org, or simultaneous?
> 

Simultaneous. You should release there before ekiga.org.

> > 2) Test them (do at least minimal tests)
> 
> Is a test on garnome on an x86 laptop sufficient?  If
not, does gnome
> have a build-test farm?

I don't know. You have to run Ekiga, even on an older
version of GNOME,
that does not matter.

> 
> > 3) Upload to GNOME.org
> > 4) Mail packagers
> > 5) Build a repository
> 
> What are the issues with the existing repositories?

The existing repositories will be built from the repository
the release
maintainer will build. Currently, each time I receive a
package, I need
to scp it to ekiga.org. That is time consuming for me. Every
release, I
loose a few hours on that instead of coding.

> > Also, regularly, that person should upload the
required OPAL and PWLIB
> > dependancies for the SVN version to GNOME.org.
> 
> How often is regularly?
> 

I don't know, really. But probably not more than once a
month.

> Can these tasks can be done by someone who is not a C
programmer?  (I
> think familiarity with configuring the dependencies,
building, tarring
> and using SVN, and simple scripting, is needed.)


Yes, you are right.

That is really a "release manager". Coding is not
required at all, it is
supposed to work already ;)
-- 
 _     Damien Sandras
(o-      
//    Ekiga Softphone : http://www.ekiga.org/
v_/_   NOVACOM         : http://www.novacom.be/
       FOSDEM          : http://www.fosdem.org/
       SIP Phone       : sip:dsandrasekiga.net
                       

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

As you guessed, I am interested in volunteering for 1 to 4
(I don't
fully understand 5 yet - questions below.))

I don't have a track record in release management.  My only
credentials are that I am interested, I know how to use
rsync and to
do CVS and SVN checkouts.   It is a long while since I built
Ekiga
from source.  Interested?

Oh - and I am based in the UK - anyone know if that could
cause patent
problems for the project?

On 6/7/07, Damien Sandras <dsandrasseconix.com> wrote:
> > Are releases to gnome.org after each release on
ekiga.org, or simultaneous?
> >
> Simultaneous. You should release there before
ekiga.org.

OK.  I can make time to do manage these releases - but not
at short
notice and not during the working day.  The key to me making
time
would be to freeze SVN (or a branch of SVN) a few days
before so that
I could have some time to make the tarballs and test them,
and double
check the uploads and links from the release announcement
and website
are ready for the release.

> > > 5) Build a repository
> >
> > What are the issues with the existing
repositories?
>
> The existing repositories will be built from the
repository the release
> maintainer will build. Currently, each time I receive a
package, I need
> to scp it to ekiga.org. That is time consuming for me.
Every release, I
> loose a few hours on that instead of coding.

Could a release manager extend the script that builds the
nightly
snapshots to also make release packages?  Does the build
script
automatically slurp the library tarballs or CVS down from
Sourceforge?

Finally, do you think the package maintainers could be
persuaded to
upload packages (or package definition files) to a stable
location?
Or do they do this already?

> > > Also, regularly, that person should upload
the required OPAL and PWLIB
> > > dependencies for the SVN version to
GNOME.org.

Where on gnome.org do copies of OPAL and PWLIB go?  I did
not find
them on svn.gnome.org.

David
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

I wrote:
> Where on gnome.org do copies of OPAL and PWLIB go?  I
did not find
> them on svn.gnome.org.

My other questions are still open, but I found two answers
to this:

First is that Damian put tarballs on ftp.gnome.org, and
asked here
this morning for a volunteer  to take on that job :

http://mail.gnome.org/archives/release-team/2
007-June/msg00020.html

Second is these locations (which don't seem to have been
updated since
GNOME 2.17, linked from the Live wiki :
http://live.gnome.org/TwoPointSeventeen/ExternalDepe
ndencies )

http://downlo
ad.gnome.org/sources/pwlib
http://downlo
ad.gnome.org/sources/opal/

I happily volunteer to upload to both of these locations,
though how
GNOME downstream users tag and link to these tarballs to
build
packages and distributions is not something I want to dig
into.

David
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Le jeudi 07 juin 2007 à 11:14 +0100, David Corking a écrit
:
> As you guessed, I am interested in volunteering for 1
to 4 (I don't
> fully understand 5 yet - questions below.))
> 

Excellent news ! 

Setting things in place will be the most difficult.

> I don't have a track record in release management.  My
only
> credentials are that I am interested, I know how to use
rsync and to
> do CVS and SVN checkouts.   It is a long while since I
built Ekiga
> from source.  Interested?

Of course !

The first things to do are :
- ask the GNOME accounts team for a SVN account, and an
account to be
able to upload to master.gnome.org. You have to ask
yourself, and put me
in CC so that I can confirm. You can see all the required
information on
http://developer.gnome.org


- take a CVS account on sourceforge.net, and give it to
Craig Southeren
so that he can give you read/write access to the CVS of OPAL
and PWLIB.

Understand the various branches :
- Ekiga 2.0.x is the "gnome-2-14" branch of the
GNOME SVN for Ekiga and
can be built with OPAL and PWLIB from the "Phobos"
branch of the
sourceforge CVS.
- Ekiga "HEAD" corresponds to OPAL and PWLIB HEAD.

You also have to understand tags. (I suggest you try getting
the sources
of Ekiga 2.0.9 with OPAL and PWLIB from CVS and SVN and
compare to our
tarballs to make sure you understand things).

> 
> Oh - and I am based in the UK - anyone know if that
could cause patent
> problems for the project?

Nope.

> 
> On 6/7/07, Damien Sandras <dsandrasseconix.com> wrote:
> > > Are releases to gnome.org after each release
on ekiga.org, or simultaneous?
> > >
> > Simultaneous. You should release there before
ekiga.org.
> 
> OK.  I can make time to do manage these releases - but
not at short
> notice and not during the working day.  The key to me
making time
> would be to freeze SVN (or a branch of SVN) a few days
before so that
> I could have some time to make the tarballs and test
them, and double
> check the uploads and links from the release
announcement and website
> are ready for the release.

It is always the case 

> > > > 5) Build a repository
> > >
> > > What are the issues with the existing
repositories?
> >
> > The existing repositories will be built from the
repository the release
> > maintainer will build. Currently, each time I
receive a package, I need
> > to scp it to ekiga.org. That is time consuming for
me. Every release, I
> > loose a few hours on that instead of coding.
> 
> Could a release manager extend the script that builds
the nightly
> snapshots to also make release packages?  Does the
build script
> automatically slurp the library tarballs or CVS down
from Sourceforge?

I don't really know, Kilian is handling that script, he is
in CC.
Notice you will have to use specific branches and tags, so
the script
should be made generic. You do not need to build on all
distributions,
you just need to create the tarballs and test.

> Finally, do you think the package maintainers could be
persuaded to
> upload packages (or package definition files) to a
stable location?
> Or do they do this already?

We could do that if somebody setups the server.

> > > > Also, regularly, that person should
upload the required OPAL and PWLIB
> > > > dependencies for the SVN version to
GNOME.org.
> 
> Where on gnome.org do copies of OPAL and PWLIB go?  I
did not find
> them on svn.gnome.org.

You need to login to master.gnome.org using ssh, upload the
tarballs there, 
then use "install-module".
-- 
 _     Damien Sandras
(o-      
//    Ekiga Softphone : http://www.ekiga.org/
v_/_   NOVACOM         : http://www.novacom.be/
       FOSDEM          : http://www.fosdem.org/
       SIP Phone       : sip:dsandrasekiga.net
                       

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Le jeudi 07 juin 2007 à 11:33 +0100, David Corking a écrit
:

[...]

> I happily volunteer to upload to both of these
locations, though how
> GNOME downstream users tag and link to these tarballs
to build
> packages and distributions is not something I want to
dig into.

And it is outside of our job.
-- 
 _     Damien Sandras
(o-      
//    Ekiga Softphone : http://www.ekiga.org/
v_/_   NOVACOM         : http://www.novacom.be/
       FOSDEM          : http://www.fosdem.org/
       SIP Phone       : sip:dsandrasekiga.net
                       

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

On 6/7/07, Damien Sandras <dsandrasseconix.com> wrote:
> However, maintaining the project asks much time, and
coding asks even
> more time, so I would like to request help for one
specific task :
>
> 1) Prepare tarballs in case of release : ie Ekiga, OPAL
and PWLIB
> tarballs
> 2) Test them (do at least minimal tests)
> 3) Upload to GNOME.org
> 4) Mail packagers
> 5) Build a repository

Just thought I'd mention this: Basic instructions for 1, 3,
and 4 for
modules in general are available at
htt
p://live.gnome.org/MaintainersCorner/Releasing (those
instructions
work for all the modules I've released, though perhaps
ekiga, opal,
and pwlib having additional issues).  I'm not sure what 5
means.

Cheers,
Elijah
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

On 6/8/07, Elijah Newren <newrengmail.com> wrote:
> On 6/7/07, Damien Sandras <dsandrasseconix.com> wrote:
> > However, maintaining the project asks much time,
and coding asks even
> > more time, so I would like to request help for one
specific task :
> >
> > 1) Prepare tarballs in case of release : ie Ekiga,
OPAL and PWLIB
> > tarballs
> > 2) Test them (do at least minimal tests)
> > 3) Upload to GNOME.org
> > 4) Mail packagers
> > 5) Build a repository
>
> Just thought I'd mention this: Basic instructions for
1, 3, and 4 for
> modules in general are available at
> htt
p://live.gnome.org/MaintainersCorner/Releasing (those
instructions
> work for all the modules I've released, though perhaps
ekiga, opal,
> and pwlib having additional issues).  I'm not sure what
5 means.

Thanks Elijjah - I copied that link into the Ekiga wiki for
our future
reference.

For (5) I wrote: "The Ekiga Release Manager should make
a repository
of contributed binary packages, such as RPMs and DEBs,
available to
the webmaster of ekiga.org"

http:
//wiki.ekiga.org/index.php/Release_Manager

When I get my SVN account, I still won't be touching the
sources (even
the changelog and news files) until I know I can do it to
the
satisfaction of the established developers - my job will
relate to the
tarballs and the announcements.

On the subject of announcements:
a - do all the packagers track one of ekiga-list and
gnome-announce-list, or are their other addresses that need
cc'd?
b - is it now deprecated to cross-post to the release-team
list ?

David
_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Le vendredi 08 juin 2007 à 10:03 +0100, David Corking a
écrit :
> On 6/8/07, Elijah Newren <newrengmail.com> wrote:
> > On 6/7/07, Damien Sandras <dsandrasseconix.com> wrote:
> > > However, maintaining the project asks much
time, and coding asks even
> > > more time, so I would like to request help
for one specific task :
> > >
> > > 1) Prepare tarballs in case of release : ie
Ekiga, OPAL and PWLIB
> > > tarballs
> > > 2) Test them (do at least minimal tests)
> > > 3) Upload to GNOME.org
> > > 4) Mail packagers
> > > 5) Build a repository
> >
> > Just thought I'd mention this: Basic instructions
for 1, 3, and 4 for
> > modules in general are available at
> > htt
p://live.gnome.org/MaintainersCorner/Releasing (those
instructions
> > work for all the modules I've released, though
perhaps ekiga, opal,
> > and pwlib having additional issues).  I'm not sure
what 5 means.
> 
> Thanks Elijjah - I copied that link into the Ekiga wiki
for our future
> reference.
> 
> For (5) I wrote: "The Ekiga Release Manager should
make a repository
> of contributed binary packages, such as RPMs and DEBs,
available to
> the webmaster of ekiga.org"
> 
> http:
//wiki.ekiga.org/index.php/Release_Manager
> 
> When I get my SVN account, I still won't be touching
the sources (even
> the changelog and news files) until I know I can do it
to the
> satisfaction of the established developers - my job
will relate to the
> tarballs and the announcements.
> 
> On the subject of announcements:
> a - do all the packagers track one of ekiga-list and
> gnome-announce-list, or are their other addresses that
need cc'd?

Once the tarballs are available somewhere, you can mail the
packagers.
(by private e-mail).

When we have enough packages, we usually do the release and
announce it
everywhere (including gnome-announce-list).

> b - is it now deprecated to cross-post to the
release-team list ?

I don't know 

-- 
 _     Damien Sandras
(o-      
//    Ekiga Softphone : http://www.ekiga.org/
v_/_   NOVACOM         : http://www.novacom.be/
       FOSDEM          : http://www.fosdem.org/
       SIP Phone       : sip:dsandrasekiga.net
                       

_______________________________________________
Ekiga-devel-list mailing list
Ekiga-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list