Re: [jQuery] JQuery Forge

[Jörn Zaefferer]

Mike Hostetler schrieb:
> Very cool requirements.  I am more then happy to take the lead on this 
> and even sponsor the hosting on my servers, or work on others servers.
You might want to keep them in mind and discuss the rest with John :-)

-- Jörn

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] JQuery Forge

[Mike Hostetler]

Jörn- Very cool requirements.  I am more then happy to take the lead on this and even sponsor the hosting on my servers, or work on others servers.  
MikeOn 10/5/06, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
Hi Mike!> A thread a while back mentioned a jQuery Forge website.  I have built> a forge type website with Drupal for another open source project I'm> involved with called Qcodo.  That website is at
> http://qforge.qcodo.com .>> I wanted to bring the issue back up because I still see people asking
> about it.  If this is already in the works, I don't want to step on> anyones toes.  Additionally, if John is working on something like> this, I'd be happy to take the back seat to whatever he wants to do.
>> So, is there any interest in a forge type website with Subversion> hosting, written on top of Drupal?  Each project (or plugin) would> have it's own site along with issue tracking and control of their
> piece of the SVN repository.>> Is there anyone out there that would be willing to help with this too?To my knowlegde, there are several plans for something like this, but sofar no implementations, though I'm not sure what Paul and John are up to
about the new jQuery site. I think it would be great if you couldprovide a prototype for a jQuery forge. Apart from hosting projects andproviding (restrictable) subversion access, there should be some way to
integrate the jQuery build system. Apart from some small issues, thecurrent ant build can be easily used to build plugins and bundle themwith jQuery into one file. It would be great if this build could betriggered by the jQuery forge...
The most basic requirement would be the ability to launch a java processon the server. From what I have seen after a quick look at the qcodo forge: Groovy!Seems to provide most of the requirements I had in mind. See below for
details.-- Jörn*'jQuery community' is my working name for the basic idea of a centralplugin repository.*It provides the following use cases or rather roles.Parts in italic are more experimental thoughts.
*Anonymous user*An anonymous user browses for plugins, either by listing them(alphabeticaly; ranked by votes or downloads; category), searching bykeywords (title; title & description) or looking for dependencies (list
all dependencies of a certain plugin; list all plugins, that depend on acertain plugin).For a given plugin, he can download all released version of that pluginand can give an anonymous vote. He can read the provided documentation
and examples. He can try out the plugin in a sandbox enviroment withoutdownloading any code (see w3schools.com for examples, eg.
http://www.w3schools.com/js/tryit.asp?filename=tryjs_function2 ). /Thesandbox provides either enough generic markup to demonstrate the pluginor provides markup created with the plugin in mind./He can read the public forums.
He can register to become a registered user.*Registered user*In addition to the possibilites of the anonymous user (minus theregistering), the registered user vote for plugins. He can vote onlyonce per plugin, but can modify he vote later on. This allows him to
correct his vote if he knows more about the plugin or if some seriousbugs were fixed, new features added etc. The vote of a registered userweighs either more than the anonymous one or is registered/counted as a
seperate vote.He can both read and write in the public forums.He can check out trunk versions from the svn repository, if one is used(see below).He can write comments (praise, flame, feature requests) and bug reports
for every plugin. In addition, he can write comments for every pluginproject (explained soon).He can create a new plugin project. A plugin project consists of one ormore plugins (eg. Interface is a plugin project, draggable is considered
a plugin). To create the project, he must provide at least a shortdescription of the purpose of the project. The create request is thenreviewed by a moderator (see below).With a created and approved project, he can do the following:
Upload files via forms or SVN. When uploading via forms, he can choosewheather warnings should be displayed when overwriting files; hisdecision is remembered. To use SVN, he must request svn access. This can
be either approved automaticaly or by a moderator. /There is no need tocreate a repository when it isn't used. On the other hand, it can beconsidered to commit files uploaded via forms to a svn repository on the
server side./After commiting files, he can create a release. The initial versionnumber is either 1.0 or 0.1. When creating new releases, he can choosebetween creating minor and major releases. Minor releases increase minor
version, eg. 1.0 to 1.1 or 1.59 to 1.60. Major releases increase themajor version, eg. 1.2 to 2.0. He should choose a minor release whenusers can update the plugin without changing their own code. He should
create a major release when users have to change their own code in orderto upgrade.When creating releases, API documentat

Re: [jQuery] JQuery Forge

[Jörn Zaefferer]

Hi Mike!
> A thread a while back mentioned a jQuery Forge website.  I have built 
> a forge type website with Drupal for another open source project I'm 
> involved with called Qcodo.  That website is at 
> http://qforge.qcodo.com . 
>
> I wanted to bring the issue back up because I still see people asking 
> about it.  If this is already in the works, I don't want to step on 
> anyones toes.  Additionally, if John is working on something like 
> this, I'd be happy to take the back seat to whatever he wants to do. 
>
> So, is there any interest in a forge type website with Subversion 
> hosting, written on top of Drupal?  Each project (or plugin) would 
> have it's own site along with issue tracking and control of their 
> piece of the SVN repository.
>
> Is there anyone out there that would be willing to help with this too?
To my knowlegde, there are several plans for something like this, but so 
far no implementations, though I'm not sure what Paul and John are up to 
about the new jQuery site. I think it would be great if you could 
provide a prototype for a jQuery forge. Apart from hosting projects and 
providing (restrictable) subversion access, there should be some way to 
integrate the jQuery build system. Apart from some small issues, the 
current ant build can be easily used to build plugins and bundle them 
with jQuery into one file. It would be great if this build could be 
triggered by the jQuery forge...
The most basic requirement would be the ability to launch a java process 
on the server.

 From what I have seen after a quick look at the qcodo forge: Groovy! 
Seems to provide most of the requirements I had in mind. See below for 
details.

-- Jörn


*'jQuery community' is my working name for the basic idea of a central 
plugin repository.*

It provides the following use cases or rather roles.
Parts in italic are more experimental thoughts.

*Anonymous user*
An anonymous user browses for plugins, either by listing them 
(alphabeticaly; ranked by votes or downloads; category), searching by 
keywords (title; title & description) or looking for dependencies (list 
all dependencies of a certain plugin; list all plugins, that depend on a 
certain plugin).
For a given plugin, he can download all released version of that plugin 
and can give an anonymous vote. He can read the provided documentation 
and examples. He can try out the plugin in a sandbox enviroment without 
downloading any code (see w3schools.com for examples, eg. 
http://www.w3schools.com/js/tryit.asp?filename=tryjs_function2 ). /The 
sandbox provides either enough generic markup to demonstrate the plugin 
or provides markup created with the plugin in mind./
He can read the public forums.
He can register to become a registered user.

*Registered user*
In addition to the possibilites of the anonymous user (minus the 
registering), the registered user vote for plugins. He can vote only 
once per plugin, but can modify he vote later on. This allows him to 
correct his vote if he knows more about the plugin or if some serious 
bugs were fixed, new features added etc. The vote of a registered user 
weighs either more than the anonymous one or is registered/counted as a 
seperate vote.
He can both read and write in the public forums.
He can check out trunk versions from the svn repository, if one is used 
(see below).
He can write comments (praise, flame, feature requests) and bug reports 
for every plugin. In addition, he can write comments for every plugin 
project (explained soon).

He can create a new plugin project. A plugin project consists of one or 
more plugins (eg. Interface is a plugin project, draggable is considered 
a plugin). To create the project, he must provide at least a short 
description of the purpose of the project. The create request is then 
reviewed by a moderator (see below).
With a created and approved project, he can do the following:
Upload files via forms or SVN. When uploading via forms, he can choose 
wheather warnings should be displayed when overwriting files; his 
decision is remembered. To use SVN, he must request svn access. This can 
be either approved automaticaly or by a moderator. /There is no need to 
create a repository when it isn't used. On the other hand, it can be 
considered to commit files uploaded via forms to a svn repository on the 
server side./

After commiting files, he can create a release. The initial version 
number is either 1.0 or 0.1. When creating new releases, he can choose 
between creating minor and major releases. Minor releases increase minor 
version, eg. 1.0 to 1.1 or 1.59 to 1.60. Major releases increase the 
major version, eg. 1.2 to 2.0. He should choose a minor release when 
users can update the plugin without changing their own code. He should 
create a major release when users have to change their own code in order 
to upgrade.
When creating releases, API documentation should be parsed from the 
plugin code, just like its happening with jQu

Re: [jQuery] JQuery Forge

[John Resig]

Mike -

That's exactly the plan that I have. I'm going to contact you off-list
and we can work this out.

--John

On 10/5/06, Mike Hostetler <[EMAIL PROTECTED]> wrote:
> A thread a while back mentioned a jQuery Forge website.  I have built a
> forge type website with Drupal for another open source project I'm involved
> with called Qcodo.  That website is at http://qforge.qcodo.com .
>
> I wanted to bring the issue back up because I still see people asking about
> it.  If this is already in the works, I don't want to step on anyones toes.
> Additionally, if John is working on something like this, I'd be happy to
> take the back seat to whatever he wants to do.
>
> So, is there any interest in a forge type website with Subversion hosting,
> written on top of Drupal?  Each project (or plugin) would have it's own site
> along with issue tracking and control of their piece of the SVN repository.
>
> Is there anyone out there that would be willing to help with this too?

___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Re: [jQuery] JQuery Forge

[Larry Garfield]

I seem to recall John saying he was already planning to do exactly that. 
Although if you wanted to volunteer to do it for him, that would give him
more time to work on jQuery itself. ;-)

-- 
Larry Garfield

On Thu, October 5, 2006 11:02 am, Mike Hostetler said:
> A thread a while back mentioned a jQuery Forge website.  I have built a
> forge type website with Drupal for another open source project I'm
> involved
> with called Qcodo.  That website is at http://qforge.qcodo.com.
>
> I wanted to bring the issue back up because I still see people asking
> about
> it.  If this is already in the works, I don't want to step on anyones
> toes.
> Additionally, if John is working on something like this, I'd be happy to
> take the back seat to whatever he wants to do.
>
> So, is there any interest in a forge type website with Subversion hosting,
> written on top of Drupal?  Each project (or plugin) would have it's own
> site
> along with issue tracking and control of their piece of the SVN
> repository.
>
> Is there anyone out there that would be willing to help with this too?
>
> --
> Mike Hostetler
> [EMAIL PROTECTED]
> http://www.amountaintop.com
> ___
> jQuery mailing list
> discuss@jquery.com
> http://jquery.com/discuss/
>



___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

[jQuery] JQuery Forge

[Mike Hostetler]

A thread a while back mentioned a jQuery Forge website.  I have built a forge type website with Drupal for another open source project I'm involved with called Qcodo.  That website is at http://qforge.qcodo.com
.  I wanted to bring the issue back up because I still see people asking about it.  If this is already in the works, I don't want to step on anyones toes.  Additionally, if John is working on something like this, I'd be happy to take the back seat to whatever he wants to do.  
So, is there any interest in a forge type website with Subversion hosting, written on top of Drupal?  Each project (or plugin) would have it's own site along with issue tracking and control of their piece of the SVN repository.
Is there anyone out there that would be willing to help with this too?-- Mike Hostetler[EMAIL PROTECTED]
http://www.amountaintop.com
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/