Re: Sandbox account?

[cyberlot]

How do we want to handle the approval process and such for signups?

I think we need some sort of secure internal ticket system we can all
see to track issues and requests.

Richard Thomas - CEO
Cyberlot Technologies Group Inc.
507.398.4124 - Voice


Rob Allen wrote:
> Hi Richard,
>
> It is possible to get a sandbox account so that I can compile the docs
> for Zend_Config?
>
> Regards,
>
> Rob...
>

[GavinZend]

I remember Ole mentioned he was familiar with RT.  However, I would not
want to wait for a ticket system before allowing people to start using
the server.  Perhaps we can just use a very clunky process with wiki
pages for the moment?  It would be ugly, but very simple and requires
almost no effort to setup.

I am hoping we can launch the server before the conference at the end of
October, and think an "unconference" mini-session for those interested
in the Server Management Team's projects would be a great idea!

Cheers,
Gavin

Richard Thomas wrote:

> How do we want to handle the approval process and such for signups?
>
> I think we need some sort of secure internal ticket system we can all
> see to track issues and requests.
>
> Richard Thomas - CEO
> Cyberlot Technologies Group Inc.
> 507.398.4124 - Voice
>
>
> Rob Allen wrote:
>> Hi Richard,
>>
>> It is possible to get a sandbox account so that I can compile the docs
>> for Zend_Config?
>>
>> Regards,
>>
>> Rob...
>>
>
>

--
Cheers,
Gavin

Which ZF List?
=================
Everything, except the topics below: [hidden email]

Authorization, Authentication, ACL, Access Control, Session Management
[hidden email]

Tests, Caching, Configuration, Environment, Logging
[hidden email]

All things related to databases
[hidden email]

Documentation, Translations, Wiki Manual / Tutorials
[hidden email]

Internationalization & Localization, Dates, Calendar, Currency, Measure
[hidden email]

Mail, MIME, PDF, Search, data formats (JSON, ...)
[hidden email]

MVC, Controller, Router, Views, Zend_Request*
[hidden email]

Community Servers/Services (shell account, PEAR channel, Jabber)
[hidden email]

Web Services & Servers (HTTP, SOAP, Feeds, XMLRPC, REST)
[hidden email]


How to un/subscribe:  http://framework.zend.com/wiki/x/GgE

[Willie Alberty]

On Oct 19, 2006, at 11:37 AM, Gavin Vess wrote:

> I remember Ole mentioned he was familiar with RT.  However, I would  
> not want to wait for a ticket system before allowing people to  
> start using the server.  Perhaps we can just use a very clunky  
> process with wiki pages for the moment?  It would be ugly, but very  
> simple and requires almost no effort to setup.

Ticket system... JIRA? It can even be configured to automatically  
create issues from an e-mail account so only sysadmins would need to  
have direct access to the project.

--

Willie Alberty, Owner
Spenlen Media
[hidden email]

http://www.spenlen.com/

[GavinZend]

Richard and Ole will lead the decision regarding which ticket/request
tracker system(s) to use, and whether or not they need a private "space"
for security-sensitive information, etc.  Anything "private" would
violate the terms of the JIRA license for use with open-source
projects.  They offer a very nice "free" license for projects like ours.

If the Server Management Team chooses to make everything in the tracker
publicly readable, and they choose to use JIRA, then I will install a
JIRA project space for this purpose, if the Zend team also agrees.

Cheers,
Gavin

Ole Bendik Kvisberg wrote:

> Richard Thomas wrote:
>> Ok, so it looks like JIRA can do what we want.. Here is what I see
>> for this
>>
>> A user comes to JIRA and can submit tickets, they can only see
>> tickets they have submitted, Tickets go into a "Account Admin" que
>>
>> Account Admins can log in and view all user tickets and process them,
>> They can also submit "Server Tickets", and we would have a server que
>>
>> Us Server Admin type can log in, see both ques and manage both ques
>>
>> I think this would provide us the security and flexability that would
>> be required.
>>
>>
> JIRA seems like a nice, but quite expensive tool.
> Is there a license available?

Willie Alberty wrote:

> On Oct 19, 2006, at 11:37 AM, Gavin Vess wrote:
>
>> I remember Ole mentioned he was familiar with RT.  However, I would
>> not want to wait for a ticket system before allowing people to start
>> using the server.  Perhaps we can just use a very clunky process with
>> wiki pages for the moment?  It would be ugly, but very simple and
>> requires almost no effort to setup.
>
> Ticket system... JIRA? It can even be configured to automatically
> create issues from an e-mail account so only sysadmins would need to
> have direct access to the project.

[Willie Alberty]

On Oct 19, 2006, at 3:19 PM, Gavin Vess wrote:

> Anything "private" would violate the terms of the JIRA license for  
> use with open-source projects.  They offer a very nice "free"  
> license for projects like ours.

The JIRA Licensing FAQ regarding the open-source license does not  
appear to require that all issues contained on the JIRA instance be  
viewable by anonymous users, only that the project itself and JIRA  
exist on a publicly-accessible server:

http://www.atlassian.com/about/licensing/faq.jsp#open-source
http://www.atlassian.com/software/views/opensource-license-request.jsp

I could not find a separate open-source license document on their web  
site, only commercial and non-profit. Is there a separate open-source  
license? Is there language in that license that states that all  
issues in the server be viewable by anonymous users?

If not, I can't see that there would be a problem with creating a  
JIRA project that is used only by the server administration teams.

--

Willie Alberty, Owner
Spenlen Media
[hidden email]

http://www.spenlen.com/