Markup Minutes 2006-08-24
From MemberWiki
Contents |
Minutes from Declarative Markup committee teleconference August 24, 2006
Attendees
- Alex Russell <alex@dojotoolkit.org>
- Anil Sharma <anil@vertexlogic.com>
- Gustavo Munoz <gustavom@jackbe.com>
- James Margaris <jmargaris@nexaweb.com>
- Jon Ferraiolo <jferrai@us.ibm.com>
- Lindsey Simon <lsimon@finetooth.com>
- Phil Berkland <berkland@us.ibm.com>
- Steven Pothoven <pothoven@us.ibm.com>
- Ted Thibodeau <tthibodeau@openlinksw.com>
- Vivienne van der Vooren <vvandervooren@seagullsoftware.com>
Absent
- David Temkin <temkin@laszlosystems.com>
- Eddie O'Neil <ekoneil@bea.com>
- Dave Johnson <djohnson@ebusiness-apps.com>
- Coach Wei <coach@nexaweb.com>
- Adam Peller <apeller@us.ibm.com>
- Alejandro Escalante Medina <alejandroe@jackbe.com>
- Brodi Beartusk <bbeartus@bea.com>
- Charles Lowell <cowboyd@thefrontside.net>
- Chris Jolley <jolleyc@bea.com>
- Chuck Ames <CAmes@seagullsoftware.com>
- David Frankel <david.frankel@sap.com>
- Eric Nguyen <ericn@mercedsystems.com>
- Erik van Dongen <evandongen@seagullsoftware.com>
- Javier Gallego <Javier.Gallego@softwareag.com>
- Jeremy Chone <jchone@adobe.com>
- Jim Grandy <jgrandy@openlaszlo.org>
- John Crupi <john.crupi@jackbe.com>
- Joonas Lehtinen <joonas.lehtinen@itmill.com>
- Jorge Taylor <jotaylor@adobe.com>
- Ken Fyten <ken.fyten@icesoft.com>
- Kin Blas <jblas@adobe.com>
- Kingsley Idehen <kidehen@openlinksw.com>
- Marc Englund <marc.englund@itmill.com>
- Mark Schiefelbein <mark@backbase.com>
- Michael Peachey <mpeachey@tibco.com>
- Ruben Daniels <ruben@javeline.nl>
- Sami Ekblad <sami.ekblad@itmill.com>
- Vincent Hardy <vincent.hardy@sun.com>
- William Shulman <will@mercedsystems.com>
Agenda
- Next steps with open source project at SourceForge
- Registration submitted to SourceForge on Tuesday 8-22, approved on Wednesday 8-23
- Project name: OpenAjax Alliance
- Unix name: openajaxallianc (note: 15 char limit, already a project named "openajax")
- Wiki page with details: Open Source
- Registration submitted to SourceForge on Tuesday 8-22, approved on Wednesday 8-23
- Next face-to-face-meeting, October 5/6, Silicon Valley
- Any volunteers to host the meeting?
- New logo and web site
- Staged web site: http://www.openajaxalliance.org/member/website-staging/
- Transition email discussion to yahoogroups? (openajax_markup@yahoogroups.com)
Open source setup issues:
- SVN or CVS - Proposal: SVN
- Secure SVN? - Proposal: The SourceForge web site talks about HTTPS access to the project SVN repository. If there is an option for HTTP vs HTTPS, we want HTTPS, don't we?
- Project admins - Proposal: Jon Ferraiolo for now. Add other admins later if there is strong evidence of ongoing commitment.
- Project members - Proposal: Adopt a generally permissive approach for people who want to contribute to the project. In general, anyone who works for an OpenAjax Alliance member company is allowed to join the SourceForge project. We also allow people not associated with the Alliance to join the open source project.
- Permissions - Proposal: Initially, assume everyone on the project is professional, trustworthy and capable, which means all developers have read/write access to entire source tree. (We can put restrictions on in the future.)
- Project web site at SourceForge - Proposal: Clearly state that the mission of the SourceForge project is to implement the technologies defined by OpenAjax Alliance and to implement associated tools around those projects (e.g., JavaScript collision detection tools).
- Which trackers? - Proposal: Set up our project to support all available SourceForge trackers: Bug Reports, Support Requests, Feature Requests, user-submitted Patches.
- Forums? - Proposal: No forums at this time. Mail lists should be sufficient.
- Maillists - Proposal: Initially, create two mail lists, one for the general public and one that is private to the members of the project.
Minutes
Jon: there will be a face 2 face meeting somewhere in silicon valley after the Ajax conference, not it is not decided who will host, looking for volunteers to host a meeting of up to 100 people
Jon: marketing committee has been working on the OpenAjax website, it will be ready to go public next week, IBM is writing a press release
Jon: discussed mailing lists, made tentative decision to use yahoo groups
?: as good as any
no objections to using yahoo groups
Question if SourceForge supports mail groups?
Jon: planning to use SourceForge for mail relative to cod projects, the marketing committee doesn't care about code so would use yahoo groups,
Jon: proposes a group for each committee, uses SourceForge mailing lists for code related items?
no objections
Jon will inform marketing and iterop committees
Jon announced openajaxalliance project has been established on SourceForge
Ted: suggests name should be openajaxhub, concerned openajaxalliance is too generic, and breaks the granularity of projects
Jon: not familiar with how downloads work on SourceForge, can a project have multiple downloads? Alex: yes, can have multiple downloads
Jon: use IRC to vote on openajaxalliance vs openajaxhub
IRC vote results
<ferraiolo> +alliance <jmargaris> I prefer alliance, hub is scoped too narrowly <elsigh> +-eitheror <TedThibodeauJr> I was the initial vocal commenter... and I still think `hub` is better, as we can have multiple projects -- and it won't have the truncation issue, for one <VivVooren> I guess alliance is better as parent <Phil_Berkland> alliance <VivVooren> can have subtopics for hub etc <TedThibodeauJr> OAA owns/coordinates/sponsors projects <justavo> +alliance <slightlyoff> hub seems fine, but I don't much care <pothoven> alliance <slightlyoff> you could just shorten it to be "oaa" ;-)
Jon: At least as many votes for "alliance" as "hub", so let's leave it as "alliance" for now and check with other committees. Also, before changing any names, we have to remember that we might get to take over the "openajax" project.
(Subsequent note added by Jon: Someone mentioned that one factor to consider is that if we take on activities beyond the Hub it would be a large management hassle to have to administer multiple open source projects and share/include code across multiple open source projects.)
Open Source Setup Discussion
- SVN or CVS - Proposal: SVN
Jon: vote on IRC
<TedThibodeauJr> +SVN <VivVooren> +SVN <slightlyoff> SVN <justavo> +svn
resolved to use subversion
- Secure SVN? - Proposal: The SourceForge web site talks about HTTPS access to the project SVN repository. If there is an option for HTTP vs HTTPS, we want HTTPS, don't we?
It will be HTTPS
Someone clarified that SVN will control user access based on SourceForge userid,
- Project admins - Proposal: Jon Ferraiolo for now. Add other admins later if there is strong evidence of ongoing commitment.
There were no objections to the proposal.
Jon: would be good to have backup administrator
Lindsey: how about James
James: what does admin do?
Jon: admins can do everything
james: I can do it
Jon: James will be backup for now
- Project members - Proposal: Adopt a generally permissive approach for people who want to contribute to the project. In general, anyone who works for an OpenAjax Alliance member company is allowed to join the SourceForge project. We also allow people not associated with the Alliance to join the open source project.
(Jon adds this note on 9Sept06: in subsequent discussion, we decided that we would be careful about who was given committer access and anyone who contributes would have to provide some sort of declaration that their submissions were all proper and covered by our IPR rules.)
General agreement this is OK Lindsey: without copyright, how will preserve ability to license as apache 2 license Jon: new people click on SourceForge agreement which includes apache license
Jon: discuss "grant" terminology ?: will they make sure grant license to contributed material
issues
- apache license
- allowing non members can join project
- Permissions - Proposal: Initially, assume everyone on the project is professional, trustworthy and capable, which means all developers have read/write access to entire source tree. (We can put restrictions on in the future.)
no objections.
(Jon adds this note on 9Sept06: in subsequent discussion, we decided that we would be careful about who was given committer access and anyone who contributes would have to provide some sort of declaration that their submissions were all proper and covered by our IPR rules.)
Alex: since under SVN, everything is restorable
- Project web site at SourceForge - Proposal: Clearly state that the mission of the SourceForge project is to implement the technologies defined by OpenAjax Alliance and to implement associated tools around those projects (e.g., JavaScript collision detection tools).
comments on what web sit should say?
Alex: this is where project name comes in, making it alliance gives no meaningful project description
Jon: the website would be consistent with alliance mission, with a description of the hub as the initial alliance work
James: SVN can control subtrees, Apache just has one SVN tree, can make subtrees for subprojects
- Which trackers? - Proposal: Set up our project to support all available SourceForge trackers: Bug Reports, Support Requests, Feature Requests, user-submitted Patches.
Jon: proposes to use all trackers
no comments or objections
- Forums? - Proposal: No forums at this time. Mail lists should be sufficient.
Lindsey: forums content stays forever Alex: mail list saved by source forge, forums just available on web resolution: no forums
- Maillists - Proposal: Initially, create two mail lists, one for the general public and one that is private to the members of the project.
no objections
Action Items
Jon: need to have code submitted to project by original authors, Alex, James, Lindsey are main authors
Alex, Lindsey, and James agreed to check-in their code to SourceForge
There needs to be a wiki page to describe how become a project developer, if no one volunteers, Jon will do it
