portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tay...@apache.org
Subject cvs commit: jakarta-jetspeed-2/archives/ApachePortals/forms jetspeed-1.txt jetspeed-2.txt pluto.txt wsrp4j.txt
Date Fri, 26 Mar 2004 00:22:14 GMT
taylor      2004/03/25 16:22:14

  Added:       archives/ApachePortals/forms jetspeed-1.txt jetspeed-2.txt
                        pluto.txt wsrp4j.txt
  Log:
  Forms required for creating new projects under Apache Portals
  
  Revision  Changes    Path
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/forms/jetspeed-1.txt
  
  Index: jetspeed-1.txt
  ===================================================================
  
  The Apache Portals PMC has agreed to accept the Jetspeed-1 project.
  To aid in the process, please create these below: 
  
  [1] Mailing List (i) addresses 
  
    I.   jetspeed-1-dev@portals.apache.org
    II.  jetspeed-1-user@portals.apache.org
    III. jetspeed-1-cvs@portals.apache.org
  
  (ii) remote moderators ...
  
  David Sean Taylor (taylor@apache.org)
  
  (iii) archives 
    mbox
    I.     http://portals.apache.org/mail/jetspeed-1/dev/YYYYMM.gz
    II.    http://portals.apache.org/mail/jetspeed-1/user/YYYYMM.gz
    III.   http://portals.apache.org/mail/jetspeed-1/cvs/YYYYMM.gz
  
  (iv) options 
  
    I.   Reply-To: Header       [X] yes   [ ] no
      NOTE: jetspeed-1-cvs@portals.apache.org -> jetspeed-1-dev@portals.apache.org
    II.  Prefix in Subject      [ ] yes   [X] no
    III. Eyebrowse              [X] yes   [ ] no
    IV.  Moderation Message     [X] short [ ] long
    V.   Message Trailer        [X] yes   [ ] no
     (a).   jetspeed-1-dev@portals.apache.org
  
  =====================(CUT HERE)====================================== 
  ---------------------------------------------------------------------
  To unsubscribe, e-mail:   jetspeed-1-dev-unsubscribe@portals.apache.org
  For additional commands, e-mail: jetspeed-1-dev-help@portals.apache.org
  Apache jetspeed-1 Project -- URL: http://portals.apache.org/jetspeed-1/
  =====================(END)=========================================== 
     (b).  jetspeed-1-user@portals.apache.org
  
  =====================(CUT HERE)====================================== 
  ---------------------------------------------------------------------
  To unsubscribe, e-mail:   jetspeed-1-user-unsubscribe@portals.apache.org
  For additional commands, e-mail: jetspeed-1-user-help@portals.apache.org
  Apache jetspeed-1 Project -- URL: http://portals.apache.org/jetspeed-1/
  =====================(END)=========================================== 
     (c). jetspeed-1-cvs@portals.apache.org
  
  =====================(CUT HERE)====================================== 
  ---------------------------------------------------------------------
  To unsubscribe, e-mail:   jetspeed-1-cvs-unsubscribe@portals.apache.org
  For additional commands, e-mail: jetspeed-1-cvs-help@portals.apache.org
  =====================(END)=========================================== 
  [2] Source Tracker (i) CVS Module 
  
       /home/cvs/portals-jetspeed-1/
       /home/cvspublic/portals-jetspeed-1/
  
  or 
  
  (ii) SVN 
  
       Greg, Sander, Justin, et al ... please fill in
  
  [3] Initial Committer list 
  
  ... 
  
  [4] Issue Tracker
   (i) Bugzilla URL: http://nagoya.apache.org/bugzilla/buglist.cgi?product=jetspeed-1 
  
  or 
  
  (ii) Scarab 
  
       John or DLR ... please fill in
  
  or 
  
  (iii) Jira 
  
   per-separately releasable package
   Project Name:
   Project Lead:
   Preferred Project Abbreviation(s):
   A list of Jira accounts to mark as project developers
   ...
   [if necessary, provision can be made to have admins list different from developer list]
  
  As an example, although Jakarta Commons is a single CVS module, each
  project would be a separate Jira project, although sharing a common
  permissions schema. 
  
  Once the project is setup in Jira, it would will be responsible to
  setup its own components, versions, etc.
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/forms/jetspeed-2.txt
  
  Index: jetspeed-2.txt
  ===================================================================
  
  The Apache Portals PMC has agreed to accept the jetspeed-2 project.
  To aid in the process, please create these below: 
  
  [1] Mailing List (i) addresses 
  
    I.   jetspeed-2-dev@portals.apache.org
    II.  jetspeed-2-user@portals.apache.org
    III. jetspeed-2-cvs@portals.apache.org
  
  (ii) remote moderators ...
  
  David Sean Taylor (taylor@apache.org)
  
  (iii) archives 
    mbox
    I.     http://portals.apache.org/mail/jetspeed-2/dev/YYYYMM.gz
    II.    http://portals.apache.org/mail/jetspeed-2/user/YYYYMM.gz
    III.   http://portals.apache.org/mail/jetspeed-2/cvs/YYYYMM.gz
  
  (iv) options 
  
    I.   Reply-To: Header       [X] yes   [ ] no
      NOTE: jetspeed-2-cvs@portals.apache.org -> jetspeed-2-dev@portals.apache.org
    II.  Prefix in Subject      [ ] yes   [X] no
    III. Eyebrowse              [X] yes   [ ] no
    IV.  Moderation Message     [X] short [ ] long
    V.   Message Trailer        [X] yes   [ ] no
     (a).   jetspeed-2-dev@portals.apache.org
  
  =====================(CUT HERE)====================================== 
  ---------------------------------------------------------------------
  To unsubscribe, e-mail:   jetspeed-2-dev-unsubscribe@portals.apache.org
  For additional commands, e-mail: jetspeed-2-dev-help@portals.apache.org
  Apache jetspeed-2 Project -- URL: http://portals.apache.org/jetspeed-2/
  =====================(END)=========================================== 
     (b).  jetspeed-2-user@portals.apache.org
  
  =====================(CUT HERE)====================================== 
  ---------------------------------------------------------------------
  To unsubscribe, e-mail:   jetspeed-2-user-unsubscribe@portals.apache.org
  For additional commands, e-mail: jetspeed-2-user-help@portals.apache.org
  Apache jetspeed-2 Project -- URL: http://portals.apache.org/jetspeed-2/
  =====================(END)=========================================== 
     (c). jetspeed-2-cvs@portals.apache.org
  
  =====================(CUT HERE)====================================== 
  ---------------------------------------------------------------------
  To unsubscribe, e-mail:   jetspeed-2-cvs-unsubscribe@portals.apache.org
  For additional commands, e-mail: jetspeed-2-cvs-help@portals.apache.org
  =====================(END)=========================================== 
  [2] Source Tracker (i) CVS Module 
  
       /home/cvs/portals-jetspeed-2/
       /home/cvspublic/portals-jetspeed-2/
  
  or 
  
  (ii) SVN 
  
       Greg, Sander, Justin, et al ... please fill in
  
  [3] Initial Committer list 
  
  ... 
  
  [4] Issue Tracker
   (i) Bugzilla URL: http://nagoya.apache.org/bugzilla/buglist.cgi?product=jetspeed-2 
  
  or 
  
  (ii) Scarab 
  
       John or DLR ... please fill in
  
  or 
  
  (iii) Jira 
  
   per-separately releasable package
   Project Name:
   Project Lead:
   Preferred Project Abbreviation(s):
   A list of Jira accounts to mark as project developers
   ...
   [if necessary, provision can be made to have admins list different from developer list]
  
  As an example, although Jakarta Commons is a single CVS module, each
  project would be a separate Jira project, although sharing a common
  permissions schema. 
  
  Once the project is setup in Jira, it would will be responsible to
  setup its own components, versions, etc.
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/forms/pluto.txt
  
  Index: pluto.txt
  ===================================================================
  
  The Apache Portals PMC has agreed to accept the Pluto project out of incubator.
  To aid in the process, please create these below: 
  
  [1] Mailing List (i) addresses 
  
    I.   pluto-dev@portals.apache.org
    II.  pluto-user@portals.apache.org
    III. pluto-cvs@portals.apache.org
  
  (ii) remote moderators ...
  
  David Sean Taylor (taylor@apache.org)
  
  (iii) archives 
    mbox
    I.     http://portals.apache.org/mail/pluto/dev/YYYYMM.gz
    II.    http://portals.apache.org/mail/pluto/user/YYYYMM.gz
    III.   http://portals.apache.org/mail/pluto/cvs/YYYYMM.gz
  
  (iv) options 
  
    I.   Reply-To: Header       [X] yes   [ ] no
      NOTE: pluto-cvs@portals.apache.org -> pluto-dev@portals.apache.org
    II.  Prefix in Subject      [ ] yes   [X] no
    III. Eyebrowse              [X] yes   [ ] no
    IV.  Moderation Message     [X] short [ ] long
    V.   Message Trailer        [X] yes   [ ] no
     (a).   pluto-dev@portals.apache.org
  
  =====================(CUT HERE)====================================== 
  ---------------------------------------------------------------------
  To unsubscribe, e-mail:   pluto-dev-unsubscribe@portals.apache.org
  For additional commands, e-mail: pluto-dev-help@portals.apache.org
  Apache pluto Project -- URL: http://portals.apache.org/pluto/
  =====================(END)=========================================== 
     (b).  pluto-user@portals.apache.org
  
  =====================(CUT HERE)====================================== 
  ---------------------------------------------------------------------
  To unsubscribe, e-mail:   pluto-user-unsubscribe@portals.apache.org
  For additional commands, e-mail: pluto-user-help@portals.apache.org
  Apache pluto Project -- URL: http://portals.apache.org/pluto/
  =====================(END)=========================================== 
     (c). pluto-cvs@portals.apache.org
  
  =====================(CUT HERE)====================================== 
  ---------------------------------------------------------------------
  To unsubscribe, e-mail:   pluto-cvs-unsubscribe@portals.apache.org
  For additional commands, e-mail: pluto-cvs-help@portals.apache.org
  =====================(END)=========================================== 
  [2] Source Tracker (i) CVS Module 
  
       /home/cvs/portals-pluto/
       /home/cvspublic/portals-pluto/
  
  or 
  
  (ii) SVN 
  
       Greg, Sander, Justin, et al ... please fill in
  
  [3] Initial Committer list 
  
  ... 
  
  [4] Issue Tracker
   (i) Bugzilla URL: http://nagoya.apache.org/bugzilla/buglist.cgi?product=pluto 
  
  or 
  
  (ii) Scarab 
  
       John or DLR ... please fill in
  
  or 
  
  (iii) Jira 
  
   per-separately releasable package
   Project Name:
   Project Lead:
   Preferred Project Abbreviation(s):
   A list of Jira accounts to mark as project developers
   ...
   [if necessary, provision can be made to have admins list different from developer list]
  
  As an example, although Jakarta Commons is a single CVS module, each
  project would be a separate Jira project, although sharing a common
  permissions schema. 
  
  Once the project is setup in Jira, it would will be responsible to
  setup its own components, versions, etc.
  
  
  
  1.1                  jakarta-jetspeed-2/archives/ApachePortals/forms/wsrp4j.txt
  
  Index: wsrp4j.txt
  ===================================================================
  
  The Apache Portals PMC has agreed to accept the wsrp4j project out of incubator.
  To aid in the process, please create these below: 
  
  [1] Mailing List (i) addresses 
  
    I.   wsrp4j-dev@portals.apache.org
    II.  wsrp4j-user@portals.apache.org
    III. wsrp4j-cvs@portals.apache.org
  
  (ii) remote moderators ...
  
  David Sean Taylor (taylor@apache.org)
  
  (iii) archives 
    mbox
    I.     http://portals.apache.org/mail/wsrp4j/dev/YYYYMM.gz
    II.    http://portals.apache.org/mail/wsrp4j/user/YYYYMM.gz
    III.   http://portals.apache.org/mail/wsrp4j/cvs/YYYYMM.gz
  
  (iv) options 
  
    I.   Reply-To: Header       [X] yes   [ ] no
      NOTE: wsrp4j-cvs@portals.apache.org -> wsrp4j-dev@portals.apache.org
    II.  Prefix in Subject      [ ] yes   [X] no
    III. Eyebrowse              [X] yes   [ ] no
    IV.  Moderation Message     [X] short [ ] long
    V.   Message Trailer        [X] yes   [ ] no
     (a).   wsrp4j-dev@portals.apache.org
  
  =====================(CUT HERE)====================================== 
  ---------------------------------------------------------------------
  To unsubscribe, e-mail:   wsrp4j-dev-unsubscribe@portals.apache.org
  For additional commands, e-mail: wsrp4j-dev-help@portals.apache.org
  Apache wsrp4j Project -- URL: http://portals.apache.org/wsrp4j/
  =====================(END)=========================================== 
     (b).  wsrp4j-user@portals.apache.org
  
  =====================(CUT HERE)====================================== 
  ---------------------------------------------------------------------
  To unsubscribe, e-mail:   wsrp4j-user-unsubscribe@portals.apache.org
  For additional commands, e-mail: wsrp4j-user-help@portals.apache.org
  Apache wsrp4j Project -- URL: http://portals.apache.org/wsrp4j/
  =====================(END)=========================================== 
     (c). wsrp4j-cvs@portals.apache.org
  
  =====================(CUT HERE)====================================== 
  ---------------------------------------------------------------------
  To unsubscribe, e-mail:   wsrp4j-cvs-unsubscribe@portals.apache.org
  For additional commands, e-mail: wsrp4j-cvs-help@portals.apache.org
  =====================(END)=========================================== 
  [2] Source Tracker (i) CVS Module 
  
       /home/cvs/portals-wsrp4j/
       /home/cvspublic/portals-wsrp4j/
  
  or 
  
  (ii) SVN 
  
       Greg, Sander, Justin, et al ... please fill in
  
  [3] Initial Committer list 
  
  ... 
  
  [4] Issue Tracker
   (i) Bugzilla URL: http://nagoya.apache.org/bugzilla/buglist.cgi?product=wsrp4j 
  
  or 
  
  (ii) Scarab 
  
       John or DLR ... please fill in
  
  or 
  
  (iii) Jira 
  
   per-separately releasable package
   Project Name:
   Project Lead:
   Preferred Project Abbreviation(s):
   A list of Jira accounts to mark as project developers
   ...
   [if necessary, provision can be made to have admins list different from developer list]
  
  As an example, although Jakarta Commons is a single CVS module, each
  project would be a separate Jira project, although sharing a common
  permissions schema. 
  
  Once the project is setup in Jira, it would will be responsible to
  setup its own components, versions, etc.
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org


Mime
View raw message