maven-repo-maintainers mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Fox <bri...@sonatype.com>
Subject Re: how to become an approved forge
Date Thu, 15 Jul 2010 13:57:45 GMT
I'm just now back from vacation so I'll check again with Juven to see if
everything was ok.

On Tue, Jul 13, 2010 at 5:36 AM, Tony Chemit <chemit@codelutin.com> wrote:

> Hi guys,
>
> I'm coming back to have some news from you.
>
> Did you had some time to prepare the rsync list for our repository ?
>
> I do NOT want to rush you, but just know when it could be done (I have to
> plan different client releases when this will be done and then plan my
> vacancies :))
>
> Hope everything will be ok soon and thanks for your time.
>
> Tony.
>
> Le Fri, 2 Jul 2010 06:55:35 -1000,
> Brian Fox <brianf@sonatype.com> a écrit :
>
> > Tony,
> > What groupies should we look for?
> >
> > Juven did you already look at this content or was that another repo?
> >
> > Sent from my iPad
> >
> > On Jul 1, 2010, at 11:04 PM, Tony Chemit <chemit@codelutin.com> wrote:
> >
> > > Le Thu, 1 Jul 2010 18:38:37 -0400,
> > > Brian Fox <brianf@sonatype.com> a écrit :
> > >
> > >> ---------- Forwarded message ----------
> > >> From: Brian Fox <brianf@sonatype.com>
> > >> Date: Thu, Jul 1, 2010 at 6:38 PM
> > >> Subject: Re: Fw: how to become an approved forge
> > >> To: repo-maintainers@maven.apache.org
> > >>
> > >>
> > >> Hi Tony,
> > >>
> > >> Sorry I seem to have missed your direct mail.
> > >
> > > No problem :)
> > >>
> > >> The first step is to allow the maven key used by central[1] access to
> your
> > >> repo via rsync. Then we'll pull in the contents, make sure all the
> files are
> > >> signed, etc and add you to the new sync list.
> > >>
> > >> [1]http://www.ibiblio.org/maven/id_dsa.pub
> > >>
> > >
> > > Ok I add it for user maven-central on server nuiton.org
> > >
> > > You can try ssh maven-central@nuiton.org .
> > >
> > > I try a rsync and it works :
> > >
> > > rsync -r  maven-central@nuiton.org:/var/lib/nexus/storage/central-releases
> /tmp
> > >
> > > Here is more informations about your repository to synch.
> > >
> > > public url      :
> http://nexus.nuiton.org/nexus/content/repositories/central-releases/
> > > rsync server    : nuiton.org
> > > rsync user      : maven-central
> > > rsync path      : /var/lib/nexus/storage/central-releases
> > >
> > >
> > > Thanks for your help Brian and hope to be soon on Central ;)
> > >
> > > Tony.
> > >
> > >>
> > >> On Thu, Jul 1, 2010 at 4:16 AM, Tony Chemit <chemit@codelutin.com>
> wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> Oups, try on the mailing-list, not directly to Brian since no reply
> from
> > >>> him.
> > >>>
> > >>> Can somebody have a look to our request to become an approved maven
> forge.
> > >>>
> > >>> Thanks for your time.
> > >>>
> > >>> Tony.
> > >>>
> > >>>
> > >>> ----- Message Transféré -----
> > >>>
> > >>> Date: Mon, 21 Jun 2010 12:16:37 +0200
> > >>> De: Tony Chemit <chemit@codelutin.com>
> > >>> À: Brian Fox <brianf@sonatype.com>
> > >>> Sujet: Re: how to become an approved forge
> > >>>
> > >>>
> > >>> Hi Brian,
> > >>>
> > >>> I come back to you after a while...
> > >>>
> > >>> We made progress since our last chat.
> > >>>
> > >>> We have now a nexus running here [1].
> > >>>
> > >>> In this forge, there is one repository we'd like to synchronize with
> maven
> > >>> central : [2]
> > >>>
> > >>> I made some efforts to make this repository pretty clean and it now
> matches
> > >>> central pre-requires.
> > >>>
> > >>> All artifacts are gpg signed with this key [3] as required.
> > >>>
> > >>> So could you tell me what would be next step?
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Tony.
> > >>>
> > >>> [1] http://nexus.nuiton.org
> > >>> [2]
> > >>>
> http://nexus.nuiton.org/nexus/content/repositories/nuiton-central-releases/
> > >>> [3]
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE9056E22014A6ED2
> > >>>
> > >>>
> > >>> Le Mon, 25 Jan 2010 22:03:56 -0500,
> > >>> Brian Fox <brianf@sonatype.com> a écrit :
> > >>>
> > >>>> On Mon, Jan 25, 2010 at 3:03 AM, Tony Chemit <chemit@codelutin.com>
> > >>> wrote:
> > >>>>> Le Sun, 24 Jan 2010 20:14:31 -0500,
> > >>>>> Brian Fox <brianf@infinity.nu> a écrit :
> > >>>>>
> > >>>>> Hi,
> > >>>>>
> > >>>>>> I think you're missing the links you intended.
> > >>>>>
> > >>>>> Yes my mistake..., here there are :
> > >>>>>
> > >>>>> [1] http://codelutin.com
> > >>>>> [2] http://nuiton.org
> > >>>>> [3] http://chorem.org
> > >>>>> [4] http://svn.nuiton.org/svn/
> > >>>>> [5] http://maven.nuiton.org/release
> > >>>>> [6] http://hudson.nuiton.org/hudson
> > >>>>> [7] http://sonar.nuiton.org/sonar
> > >>>>> [8] http://labs.libre-entreprise.org
> > >>>>>>
> > >>>>>> The criteria currently are:
> > >>>>>> 1) forges are open to oss projects
> > >>>>> Fine for us, we already host in our maven repository other
open
> source
> > >>> projects from
> > >>>>> another open source forge [8]
> > >>>>>
> > >>>>> Actually, we do not use a maven repository manager, if it is
> necessary,
> > >>> we could
> > >>>>> use for example the nexus one.
> > >>>>>
> > >>>>> Would it be ok for you ?
> > >>>>>
> > >>>>>> 2) host multiple projects
> > >>>>> That's true for us :)
> > >>>>>
> > >>>>>> 3) have some way to enforce the quality of the artifacts
and
> > >>> signatures.
> > >>>>> Does nexus do it for us ?
> > >>>>> Our release process assures us a good project quality I think.
> > >>>>> Signature of artifacts is still new to us, but we incoporate
it to
> > >>> release time from now.
> > >>>>
> > >>>> Nexus Pro does enforce the signature quality of the artifacts if
you
> > >>>> use the staging support, and you can get an OSS license for public
> oss
> > >>>> use on forges.
> > >>>>
> > >>>> I looked through your repos and there are a lot of artifacts that
> > >>>> probably shouldn't be there, including snapshots. I think getting
> > >>>> those imported and sorted out in a repo manager is a good first
> step.
> > >>>> We could then pick up the org/nuiton and org/chorem (and other
> > >>>> original) folders. There appear to be enough subprojects for this
> repo
> > >>>> to qualify. We're just trying to avoid having syncs setup for
> > >>>> individual projects.
> > >>>>>
> > >>>>> Best regards,
> > >>>>>
> > >>>>>> On Sun, Jan 24, 2010 at 12:49 PM, Tony Chemit <
> chemit@codelutin.com>
> > >>> wrote:
> > >>>>>>> Hello,
> > >>>>>>>
> > >>>>>>> Our company Code Lutin [1] produces some LGPL and GPL
projets
> using
> > >>> maven.
> > >>>>>>>
> > >>>>>>> We actually maintains :
> > >>>>>>>
> > >>>>>>> - two forges (Nuiton [2] , Chorem [3]),
> > >>>>>>> - a svn repostiroy [4],
> > >>>>>>> - our release repository [5] (groups org.nuiton and
org.chorem).
> > >>>>>>> - hudson for ci [6]
> > >>>>>>> - sonar [7]
> > >>>>>>>
> > >>>>>>> About our artifacts, respects I think all quality requirements
to
> go
> > >>> to
> > >>>>>>> central :
> > >>>>>>>
> > >>>>>>> - complete poms (complete projet info, scm, self-contained)
> > >>>>>>> - deploy sources + jar
> > >>>>>>> - gpg signatures (from 01-2010)
> > >>>>>>>
> > >>>>>>> We'd like to be able to synch our artifacts from org.nuiton
to
> > >>> central.
> > >>>>>>>
> > >>>>>>> Also, we don not want to host our maven repository
to an approved
> > >>> force.
> > >>>>>>>
> > >>>>>>> Can you explain us how to become an approved force.
> > >>>>>>>
> > >>>>>>> Best regards,
> > >>>>>>>
> > >>>>>>> --
> > >>>>>>>
> > >>>>>>> Tony Chemit
> > >>>>>>> --------------------
> > >>>>>>> tél: +33 (0) 2 40 50 29 28
> > >>>>>>> email: chemit@codelutin.com
> > >>>>>>> http://www.codelutin.com
> > >>>>>>>
> > >>>>>
> > >>>>> --
> > >>>>>
> > >>>>> Tony Chemit
> > >>>>> --------------------
> > >>>>> tél: +33 (0) 2 40 50 29 28
> > >>>>> email: chemit@codelutin.com
> > >>>>> http://www.codelutin.com
> > >>>>>
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> Tony Chemit
> > >>> --------------------
> > >>> tél: +33 (0) 2 40 50 29 28
> > >>> email: chemit@codelutin.com
> > >>> http://www.codelutin.com
> > >>>
> > >>>
> > >>> --
> > >>> Tony Chemit
> > >>> --------------------
> > >>> tél: +33 (0) 2 40 50 29 28
> > >>> email: chemit@codelutin.com
> > >>> http://www.codelutin.com
> > >>>
> > >
> > >
> > >
> > > --
> > > Tony Chemit
> > > --------------------
> > > tél: +33 (0) 2 40 50 29 28
> > > email: chemit@codelutin.com
> > > http://www.codelutin.com
>
>
>
> --
> Tony Chemit
> --------------------
> tél: +33 (0) 2 40 50 29 28
> email: chemit@codelutin.com
> http://www.codelutin.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message