Re: [uportal-dev] JA-SIG Weather Portlet

[Eric Dalquist]

Currently there are 3 groups in svn. On is general committers and the other two are for CAS. ScottB manages the two CAS groups and the general group is used for uPortal, portlet and channel developers. The consensus among the uPortal developers when the switch to SVN was made that it wasn't worth our time to micro-manage commit access since everyone can see what everyone else is doing it is easy enough to roll back changes if someone does something bad.

-Eric



Cris J Holdorph wrote:

That said we can always re-visit this policy and see if it makes sense to continue on this general committer role path or if we want to break up access into more granular bits. Personally my vote would be for keeping it general until such time that we actually have a problem or see ourselves growing beyond the handful of committers we have now.

This question has nothing to do specifically with Dustin per se. But to be able to answer the question, fully informed...

---- Cris J H

Eric Dalquist wrote:

If we grant commit access to something like the WeatherPortlet area, are we granting commit access to the rest of uPortal and other JA-SIG resources. Whatever the answer is, should this be true? What about the reverse? If we create the WeatherPortlet svn module, will all uPortal commiters have commit access to it? Whatever the answer is, should this be true?

This sounds great Dustin!

I'd like to propose the following
-Give Dustin svn commit access

-Create a sandbox svn module https://www.ja-sig.org/svn/sandbox/WeatherPortlet The portlet would get moved to the portlets/ directory as of the first RC -Create a child page of the Portlets wiki space to be the parent page for weather portlet content: http://www.ja-sig.org/wiki/display/PLT/Home

-Create a WeatherPortlet Jira project in the portlets group





-Eric


Dustin S. wrote:

Should we also look at creating weather portlet mailing lists or should we follow up on creating the [EMAIL PROTECTED] list and use that until there is a need for a project specific list? Please let me know what you think. Also I'm heading out on vacation later today until Monday so I won't be available for actually doing any of this resource allocation until I get back. If consensus on the list is reached others with access should feel free to do the allocation & creation.

Hi all,



Project Objectives:

    * A JSR-168 portlet that
          o can retrieve international weather and display that
            information in a user friendly format
          o can be used commercially and non-commercially
          o has a well structured design/interface so others may
            implement their own weather services if they wish

Project Technologies:

    * Spring Framework
    * Maven 2

Current Members involved:

    * Myself (Dustin)
    * Erin Garlock from CampusEAI
    * Anyone else that would like to help...everyone is welcome.



Thanks,
Dustin.
--

We have been discussing creating a weather portlet for inclusion to uPortal 3 on the uportal-user list and I'd like to move that conversation to the uportal-dev list as it is progressing. This email is to alert everyone to the creation of the project and to request resources (SVN, JIRA, Wiki) to support and begin development. You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev

smime.p7s
Description: S/MIME Cryptographic Signature