headers
Apache Wiki | 1 Jul 2005 08:07
Picon
Favicon

[Jakarta Wiki] Update of "Migrating to Subversion" by HenriYandell

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for change notification.

The following page has been changed by HenriYandell:
http://wiki.apache.org/jakarta/Migrating_to_Subversion

The comment on the change is:
Slide migrated, Taglibs in process.

------------------------------------------------------------------------------
   * Cactus            - Vincent Massol. Renudged.
   * JMeter            - Nudge sent.
   * POI               - Nudged. Is OS X support good enough? amongst other questions.
-  * Slide             - Stefan Lützkendorf. Migration applied for.
-  * Taglibs           - Tim O'Brien. Martin Cooper. [http://brahe.discursive.com/svn/taglibs/ Test Repo]
[http://brahe.discursive.com/taglibs-convert.tgz scripts.tgz(200k)]
+  * Taglibs           - Tim O'Brien. Martin Cooper. [http://brahe.discursive.com/svn/taglibs/ Test Repo]
[http://brahe.discursive.com/taglibs-convert.tgz scripts.tgz(200k)] (in process)
   * Tapestry          - Nudged. Is [http://sublicpse.tigris.org/ Subclipse] good enough?
   * Turbine           - Henning Schmiedehausen, Daniel Rall

 <at>  <at>  -58, +57  <at>  <at> 

   * ORO               - Daniel Savarese
   * Regexp            - Henri Yandell
   * Site2             - Tim O'Brien + Henri Yandell - ["Site2 Conversion Instructions"]
+  * Slide             - Stefan Lützkendorf. 
   * Velocity          - Daniel Rall
(Continue reading)

Permalink | Reply | 0 comments |
headers
Apache Wiki | 1 Jul 2005 08:09
Picon
Favicon

[Jakarta Wiki] Update of "JakartaBoardReport-September2005" by HenriYandell

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for change notification.

The following page has been changed by HenriYandell:
http://wiki.apache.org/jakarta/JakartaBoardReport-September2005

The comment on the change is:
Work in progress.

------------------------------------------------------------------------------

  === Releases ===

+  * 28 June 2005 - HiveMind 1.1-beta-2 Released
+  * 26 June 2005 - Commons HttpClient 3.0rc3 Released
+  * 25 June 2005 - Tapestry 4.0-beta-1 Released 
+ 
  === Community changes ===

  === Infrastructure news ===
+ 
+ SVN Migrations:
+ 
+     * Slide complete.

  === Subproject news ===
Permalink | Reply | 0 comments |
headers
Curt Arnold | 1 Jul 2005 08:55
Picon
Favicon

Dormant guidelines proposal?

There has been some discussion about modifying the Logging Services  
project bylaws (http://logging.apache.org/site/bylaws.html) to  
address some concerns particular to the project.  I was researching  
the Jakarta guidelines and stumbled across http://jakarta.apache.org/ 
site/proposal.html.  It is referenced at the bottom of  http:// 
jakarta.apache.org/site/guidelines.html as a working proposal, but it  
does not appear from the SVN log to have any activity for over two  
years.

Was there a resolution on the proposal?  If so or if has been  
abandoned, then it might be good to pull it and the link from the  
site or at least update the status.  Has the activity moved elsewhere  
or is it just sleeping?  If either was going to be considered as a  
starting point for a rework of the LS bylaws, would you recommend the  
proposal or the accepted guidelines?

I haven't had a chance to attempt to compare and contrast the current  
and proposed guidelines, but the proposal's one page format left a  
better impression since you can see everything at one glance.

One of significant differences between our current bylaws and either  
of the proposal or existing guidelines is that the PMC is tasked with  
electing new committers.  There is a desire to move that decision  
towards the sub-project, but I'm concerned that without any role for  
the PMC and no private medium for the vote, that there isn't a clean  
way for the PMC to address a potential disruptive or legally  
entangling committer candidate except to accept the sub-project vote  
and for the PMC to attempt to revoke his committer rights requiring a  
full consensus.  There would also be no private forum to discuss any  
sensitive issues since only the PMC has a private list.   For the LS
(Continue reading)

Permalink | Reply | 1 comment |
headers
Apache Wiki | 1 Jul 2005 15:53
Picon
Favicon

[Jakarta Wiki] Update of "Migrating to Subversion" by TimObrien

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta Wiki" for change notification.

The following page has been changed by TimObrien:
http://wiki.apache.org/jakarta/Migrating_to_Subversion

------------------------------------------------------------------------------
   * Cactus            - Vincent Massol. Renudged.
   * JMeter            - Nudge sent.
   * POI               - Nudged. Is OS X support good enough? amongst other questions.
-  * Taglibs           - Tim O'Brien. Martin Cooper. [http://brahe.discursive.com/svn/taglibs/ Test Repo]
[http://brahe.discursive.com/taglibs-convert.tgz scripts.tgz(200k)] (in process)
+  * Taglibs           - Henri Yandell using Adapted Commons Scripts  [http://brahe.discursive.com/svn/taglibs/
Test Repo] [http://brahe.discursive.com/taglibs-convert.tgz scripts.tgz(200k)] (in process)
   * Tapestry          - Nudged. Is [http://sublicpse.tigris.org/ Subclipse] good enough?
   * Turbine           - Henning Schmiedehausen, Daniel Rall
Permalink | Reply | 0 comments |
headers
Fredrik Westermarck | 1 Jul 2005 19:21
Picon
Picon
Favicon

[site] Added svn resource to library.xml

Hi!

Is there a BZ or Jira where one can open issues and add patches to the 
jakarta-site module? Or is all such requests handled on this ml?

Regards,
Fredrik Westermarck
Permalink | Reply | 3 comments |
headers
Henri Yandell | 1 Jul 2005 20:54

Re: [site] Added svn resource to library.xml


Even if there is a BZ (unsure), I doubt anyone checks it out.

This mailing list is the best place.

Hen

On Fri, 1 Jul 2005, Fredrik Westermarck wrote:

> Hi!
>
> Is there a BZ or Jira where one can open issues and add patches to the 
> jakarta-site module? Or is all such requests handled on this ml?
>
> Regards,
> Fredrik Westermarck
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe <at> jakarta.apache.org
> For additional commands, e-mail: general-help <at> jakarta.apache.org
>
Permalink | Reply | 2 comments |
headers
Martin Cooper | 2 Jul 2005 20:02
Picon
Gravatar

Re: sandbox [WAS Re: [PROPOSAL] subproject that's a home for bricks reusable in java web applications]

On 6/25/05, Stephen Colebourne <scolebourne <at> btopenworld.com> wrote:
> Rahul Akolkar wrote:
> >>is boils down to the question: does this subproject need it's own
> >>sandbox or will neophyte components start in the jakarta commons
> >>sandbox?
> >
> > +1 for sandbox (non-binding)
> >
> > Its slightly hard to imagine anything otherwise, but maybe I'm just
> > used to seeing how commons and taglibs work. If Taglibs join, we have
> > a bunch of Taglibs in sandbox, they will need to be housed somewhere,
> > and I don't see them migrating to commons sandbox ;-) Right?
> 
> Yes, +1 to a sandbox. Although it can create issues, I think has more
> benefits than downsides.

+1

--
Martin Cooper

> Stephen
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe <at> jakarta.apache.org
> For additional commands, e-mail: general-help <at> jakarta.apache.org
> 
>
Permalink | Reply | 0 comments |
headers
Martin Cooper | 2 Jul 2005 20:05
Picon
Gravatar

Re: [POLL] drop point 12 [WAS Re: [PROPOSAL] subproject that's a home for bricks reusable in java web applications]

On 6/25/05, Stephen Colebourne <scolebourne <at> btopenworld.com> wrote:
> robert burrell donkin wrote:
> > this has proved impractical in the jakarta commons. i propose we drop
> > point 12.
> 
> "12. The subproject will also provide a single JAR of all stable package
> releases. It may also provide a second JAR with a subset of only JDK 1.1
> compatible releases. A gump of nightly builds will also be provided."
> 
> >
> > --8<-----------------------------------------------------------
> > [X] +1 Get rid!
> > [ ] -1 Keep it (please give a reason...)
> > --------------------------------------------------------------
> 
> One jar didn't work for commons, no reason to expect it will here.

+1. Let's ditch it.

--
Martin Cooper

> Stephen
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe <at> jakarta.apache.org
> For additional commands, e-mail: general-help <at> jakarta.apache.org
> 
>
(Continue reading)

Permalink | Reply | 3 comments |
headers
Martin Cooper | 2 Jul 2005 20:33
Picon
Gravatar

Re: mailing lists for components [WAS Re: [PROPOSAL] subproject that's a home for bricks reusable in java web applications]

On 6/23/05, robert burrell donkin <robertburrelldonkin <at> blueyonder.co.uk> wrote:
> On Wed, 2005-06-22 at 14:40 -0700, Phil Steitz wrote:
> 
> > 4.1 in the guidelines repeats the error that I thought was fixed in the
> > j-c guidelines saying that each package has its own mailing list.  If
> > that is intentional, I think that is a *bad* idea, especially to start.
> 
> it was intentional in as much as it was a copy of the jakarta commons
> charter :)
> 
> > Don't like the many little lists implied by 11 -- dev + user works fine
> > in j-c (I know some disagree, but I personally view this as the key to
> > the health of j-c)
> 
> i agree. just dev and user lists.
> 
> in jakarta commons, the common mailing lists hold together the single
> community. i'd like to see just one mailing list with components using
> prefixing (as per jakarta commons). i'd like to see changes to the draft
> so that it's clear that this will be the arrangement.
> 
> opinions?

+1 to just one dev and one user list, shared for all components, a la
Jakarta Commons.

--
Martin Cooper

> - robert
(Continue reading)

Permalink | Reply | 2 comments |
headers
Martin Cooper | 2 Jul 2005 20:52
Picon
Gravatar

Re: new components [WAS Re: [PROPOSAL] subproject that's a home for bricks reusable in java web applications]

On 6/23/05, robert burrell donkin <robertburrelldonkin <at> blueyonder.co.uk> wrote:
> On Wed, 2005-06-22 at 14:40 -0700, Phil Steitz wrote:
> 
> <snip>
> 
> > Interpreted literally, 17 goes against standard practice in jakarta (or
> > apache, to my knowledge, other than in the incubator).  I would
> > recommend that new packages require existing committers to support them.
> > I would at least recommend changing "Anyone" to "Any apache committer."
> >      If an individual has already contributed enough to be voted in as a
> > committer, then that should be done in a separate VOTE.
> 
> this certainly doesn't reflect the current practise in the jakarta
> commons. though anyone can propose a new component, they really won't
> have any chance of winning a VOTE unless they have the support of
> existing committers.
> 
> there is also the issue of the incubator: any new component bringing
> code from outside apache would need to be incubated.

We have a few different scenarios here, I believe.

1) A new component is proposed, with no existing code to back it up.
I'm not sure that this has ever happened in Jakarta Commons, or is
likely to happen in the new subproject, so frankly I don't much care
about how that would work. ;-)

2) A new component is proposed by an existing Apache committer. This
will almost certainly be backed up by code in the sandbox.
Historically, in Jakarta Commons, there hasn't so much been a
(Continue reading)

Permalink | Reply | 9 comments |

Gmane