nice if it could be
> > automatic.
> > Everything else is really just undoing what was done during the move to
> > Attic, and is so exceptional that I don't see much value in writing.
> > But once we have a Git mirror, this will provide PRs and review process,
> > p
ite has currently to be manual, it would be nice if it could be
> automatic.
> Everything else is really just undoing what was done during the move to
> Attic, and is so exceptional that I don't see much value in writing.
> But once we have a Git mirror, this will provide PRs and review
exceptional that I don't see much value in writing.
But once we have a Git mirror, this will provide PRs and review process,
perhaps there will be good PRs proposed, finding the right balance
Regards,
Hervé
On 2022/07/04 07:14:12 Roman Shaposhnik wrote:
> On Mon, Jul 4, 2022 at 9:57 AM Brahma Re
with the something like following for future
> reference.(Might not very critical but i feel it's better to have as doc
> persist longer)
>
> " TLP project can be revived as TLP again if three ASF members are
> involved to bring it back".
>
>
> Currently the contributi
to have as doc
persist longer)
" TLP project can be revived as TLP again if three ASF members are
involved to bring it back".
Currently the contribution process is unknown to me as the attic is based
on SVN, any pointers here..?
and any chance to move to git..?
1.https://attic.apac
Le vendredi 14 mai 2021, 13:59:22 CEST sebb a écrit :
> On Fri, 14 May 2021 at 06:34, Hervé BOUTEMY wrote:
> > Hi all,
> >
> > I just finished Trafodion's move to Attic: it was a lot easier than 1 year
> > ago, being helped by 2 nice scripts. But the process docume
On Fri, 14 May 2021 at 06:34, Hervé BOUTEMY wrote:
>
> Hi all,
>
> I just finished Trafodion's move to Attic: it was a lot easier than 1 year
> ago,
> being helped by 2 nice scripts. But the process documentation did not mention
> these scripts, then showed previous comp
Hi all,
I just finished Trafodion's move to Attic: it was a lot easier than 1 year ago,
being helped by 2 nice scripts. But the process documentation did not mention
these scripts, then showed previous complexity.
I updated the documentation to take these scripts into account. Please review
On Mon, 23 Jul 2018, Ralph Goers wrote:
Date: Mon, 23 Jul 2018 15:24:58 +0200
From: Ralph Goers
To: general@attic.apache.org
Subject: Re: Clarifying the process for PMCs adopting codebases from the Attic
On Jul 23, 2018, at 1:47 AM, Bertrand Delacretaz wrote:
As for having a Board
> On Jul 23, 2018, at 1:47 AM, Bertrand Delacretaz
> wrote:
>
> As for having a Board decision when reviving a project, that probably
> makes sense for symmetry with the Board resolution that moved the
> project to the Attic. But I don't think the Board necessarily needs to
> be involved in
On Mon, 23 Jul 2018, Bertrand Delacretaz wrote:
Date: Mon, 23 Jul 2018 10:47:59 +0200
From: Bertrand Delacretaz
To: general@attic.apache.org
Subject: Re: Clarifying the process for PMCs adopting codebases from the Attic
Hi Bertrand,
thanks for the notes.
On Fri, Jul 20, 2018 at 6:40 AM
Hi,
On Fri, Jul 20, 2018 at 6:40 AM Henk P. Penning wrote:
> ... This name change is exactly what POI wanted to avoid ;
>XMLbeans users want (maven-name-space) continuity ; not change.
>The fact that XMLbeans is "under new management" should not be
>visible to users ; project
ect, also called sub-
project, the PMC does not ask any vote from board.
notice: I won't fight against a Board vote: the next time, since Board will
better know what it votes about, the vote will just be a formal approval "from
the top of ASF"
I like Bertrands's summary start: once consensu
> > Subject: Clarifying the process for PMCs adopting codebases from the
> Attic
>
> Hi Bertrand,
>
>thanks for your help ; appreciated.
>
> > I just subscribed here - we had a discussion about this at yesterday's
> > Board meeting (thanks Henk for joining that
On Thu, 19 Jul 2018, Bertrand Delacretaz wrote:
Date: Thu, 19 Jul 2018 14:43:05 +0200
From: Bertrand Delacretaz
To: general@attic.apache.org
Subject: Clarifying the process for PMCs adopting codebases from the Attic
Hi Bertrand,
thanks for your help ; appreciated.
I just subscribed here
On Thu, 19 Jul 2018, Mark Murphy wrote:
Date: Thu, 19 Jul 2018 17:55:51 +0200
From: Mark Murphy
To: general@attic.apache.org
Subject: Re: Clarifying the process for PMCs adopting codebases from the Attic
I don't know why you are trying so hard to keep XMLBeans dead. XMLBeans has
been revived
I don't know why you are trying so hard to keep XMLBeans dead. XMLBeans has
been revived by the POI PMC, not just for benefit of POI, but for whomever
needs updates. The updates benefit everyone, but keeping it in the attic
makes it look dead. This will be confusing to everyone who wants to use
Hi Attic team,
I just subscribed here - we had a discussion about this at yesterday's
Board meeting (thanks Henk for joining that), I think it's good to
clarify this and here looks like the best place.
IIUC the first occurence that just happened is
https://issues.apache.org/jira/browse/ATTIC-169
On Fri, 13 Apr 2018, Jan Iversen wrote:
Date: Fri, 13 Apr 2018 08:35:23 +0200
From: Jan Iversen <jancasacon...@gmail.com>
To: Henk P. Penning <penn...@uu.nl>
Cc: general@attic.apache.org
Subject: Re: process
Hi Jan,
Done.
Nice work !
Thanks.
typo : touch docsflagged =&g
See http://attic.apache.org/process.html for a document on how to move
a project into the Attic.
Feel free to beat it up :)
Hen
On Jan 6, 2009, at 7:04 AM, Ralph Goers wrote:
On Jan 6, 2009, at 1:54 AM, Henri Yandell wrote:
I think the path lies in between the two views.
We're not out to kill user lists outright imo. A project becomes
viable for the Attic when it has no developer community. It may still
have user
21 matches
Mail list logo
