|
Author
|
Message
|
|
Kristof Coomans
Moderated by: Nicolas Pastorino
|
Tuesday 07 November 2006 12:10:22 am
Dear community members The projects section which has been announced earlier on the forum (<i>http://ez.no/community/forum/general/new_project_section_on_ez_no</i>) is on it's way! eZ systems and I agreed that I will take care of a first release, which is planned before the end of the year. The first release will replace the current contributions section on ez.no and the community repository on pubsvn. The included features are:
General framework for creating projects, including:
- contributor information
- contact form (~ contact form for article authors, already implemented on ez.no)
- access control, based on roles inside a project: leader / member / customer
Project tools:
- news
- changelog ~
- galleries
- subversion repository
- forums
- files (~ similar to current feature in the contributions section, will be improved later) A command line script will migrate the old contributions to the projects section. The contributors who are using the subversion community repository on pubsvn (< 20) will move their source code to their project's repository. The community repository will remain readable, but write access will be denied. The projects section will be an important step for the community. A document with some technical implementation details is available at http://pubsvn.ez.no/projects/plain_site_user/ezprojects/files/implementation_details . Some code is already available at http://pubsvn.ez.no/projects/plain_site_user/ezprojects/subversion . You will find a brief installation guide at http://pubsvn.ez.no/projects/plain_site_user/ezprojects/wiki/installation. Please take some time to review the implementation details and the code. You can give feedback in this forum topic. Think critical, don't spare me :-) If something can be done in a better way then tell me. It's the community's project tool ! Cheers Kristof
independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org
|
|
Xavier Dutoit
|
Tuesday 07 November 2006 3:45:22 am
Hi, What about bugs ? When the bugs where managed into ez publish, they created a contrib category. Unfortunately, the bugs reported them never found their way to the real devs of the contribs. Don't know about the new bug system, but it'd be great if it'd be used for the projects as well. Moreover, as the number of contrib grows, it's really difficult for a new commer to know what extensions are really used or just there as exemples or to solve a very specific point. It'd be nice to be able to qualify them better. Some extensions are so usefull they should be "core" flaged. Don't know if this is some kind of tag system that users can update, or if we need a few moderators/editors on this section or a mix of that. Another thing that'd be great is to ease the update/installation process. It would be brilliant if I could automatically see the list of contribs and download a contrib into my extension area from my back-office. Moreover, it'd great to see if there has been an update on the extensions I have installed. That's all for now. X+
http://www.sydesy.com
|
|
Kristof Coomans
|
Tuesday 07 November 2006 11:06:39 am
Hi Xavier Thanks for your input.
What about bugs ?
When the bugs where managed into ez publish, they created a contrib category. Unfortunately, the bugs reported them never found their way to the real devs of the contribs.
Can you clarify this? I'm not sure I understood you correctly.
Don't know about the new bug system, but it'd be great if it'd be used for the projects as well.
We should ask the opinion of eZ systems about this. I haven't seen anything in wIT that can't be done with eZ publish and some additional PHP libraries. In any case, a project bug system (or more general: a tracking system) will not be included in the first release due to time constraints.
Moreover, as the number of contrib grows, it's really difficult for a new commer to know what extensions are really used or just there as exemples or to solve a very specific point.
It'd be nice to be able to qualify them better. Some extensions are so usefull they should be "core" flaged. Don't know if this is some kind of tag system that users can update, or if we need a few moderators/editors on this section or a mix of that.
I agree there need to be better ways to qualify the projects. Maybe we can make a hierarchical categorization of extensions, the project owner can choose more than one category his extension belongs too. For example you will have categories for the intended end users: * portal user (...) * administrator (ezjaxx, Search form in admin content/browse.tpl, http://ez.no/community/contribs/hacks/update_class_from_command_line, ...) * template writer ( http://ez.no/community/contribs/hacks/dynamic_debug, http://ez.no/community/contribs/hacks/attribute_show_identing_and_colors ) * extension developer (http://ez.no/community/contribs/applications/extension_manager) You could also have categories with different eZ publish plugable types, this would be great to search for example code:
* workflow event type
* datatype
* module
* view
* operation
* fetch function
* module policies
* search plugin
* file upload handler
* extended attribute filter
* notification event type
* notification event handler
* content action handler
* content edit handler
* template operator
* template function I can go on summing up categories for a while :-)
Another thing that'd be great is to ease the update/installation process.
It would be brilliant if I could automatically see the list of contribs and download a contrib into my extension area from my back-office.
Moreover, it'd great to see if there has been an update on the extensions I have installed.
I completely agree, installing and updating extensions should be more Mozilla-like. But this requires some serious improvements to the package manager. I don't know (yet) if eZ has any plans for this.
independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org
|
|
Sandro Groganz
|
Wednesday 08 November 2006 8:00:14 am
Let me just thank Kristof on behalf of eZ systems for his engagement! We are in close contact with him to help make real the first version of the projects section. So, whatever there is, in whatever way you think you can contribute to this, please let Kristof know and he will also coordinate with eZ if needed. Sandro
Sandro Groganz
Chief Knowledge Officer
|
|
Xavier Dutoit
|
Wednesday 08 November 2006 8:26:55 am
Can you clarify this? I'm not sure I understood you correctly.
My point is that each project needs a bug tracking kind of system. So far, that's been a mix between comments on the contrib page and forums thread that we could find if we were lucky enough. The bug section (the ez publish version) then added a category "contrib" (or something like that), but Lenara didn't forward the bug reports to the owner of the contrib (at least for my projects, for instance the eor related bugs you felt and that we discussed privately). My open question is how to deal with this bug tracker need ? Are we going to create something specific based on ez publish or do as ez systems and consider that ezpublish isn't a proper framework to deal with that and try to use their external tool ? If we want to use wit as ez, then we can see with them if that's ok for them to create the accounts, categories and bla bla bla, but we have to make that choice first. X+
http://www.sydesy.com
|
|
Paul Forsyth
|
Wednesday 08 November 2006 8:40:24 am
I would use wIT. Another project could be added for contribs. eZ is very extendable but it will take years to make an enterprise bug tracking system from it. Paul
|
|
Xavier Dutoit
|
Wednesday 08 November 2006 9:17:10 am
Hi Paul, Strong statement. Does it mean that in your mind ez shouldn't be used for things much away than content web sites ? X+
http://www.sydesy.com
|
|
Xavier Dutoit
|
Wednesday 08 November 2006 9:19:07 am
Beside, delighted to see some people from the community starting participating to this discussion. For me, how Kristof is going to do it is going to structure the community quite a bit. X+
http://www.sydesy.com
|
|
Paul Forsyth
|
Wednesday 08 November 2006 9:28:33 am
No, that was not the intent of my comment :) We simply need a good bug tracking system sooner rather than later and wIT is available. I've reviewed lots of bug systems in my time and i believe i've got a good grasp of the work involved in building one from scratch. But thats my opinion only of course. One way to accelerate an eZ solution is for eZ systems to contribute their previous bug system as a project :) Paul
|
|
Kristof Coomans
|
Thursday 09 November 2006 7:28:17 am
<b>@xavier</b>
The bug section (the ez publish version) then added a category "contrib" (or something like that), but Lenara didn't forward the bug reports to the owner of the contrib (at least for my projects, for instance the eor related bugs you felt and that we discussed privately).
I think this was my fault. I never heard of the purpose of the "contrib" category and Lenara's task to forward bugs in that category to the contrib's owner (or was this not the agreed manual workflow?). I posted those bugs in the eZ publish misc category, because the datatype was merged to the trunk at that time.
<b>@all</b>
I agree with you that a bug system is something that should be part of the project section, and better sooner than later. But I think it's currently better to spend time thinking about the general framework for setting up projects, the base on which we will build further. If this is done the right way for a first release then it will be easier to add other project tools (like trackers) in a second stage. I hope this second stage will be shortly after (2 months) a first release, but of course this also depends on the scheduling of other eZ projects.
independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org
|
|
Niklas Gunnäs
|
Thursday 07 December 2006 2:51:34 pm
Hi Kristof, How is things going with the projects section? I think it would be better to include a free bug tracker. I use ez publish because its open source and free. If the projects section was to use wits bug tracker I could not afford to install the project section on my site. And that would be a shame, at least for me ;-)
|
|
kracker (the)
|
Saturday 09 December 2006 4:06:59 am
Hey, I took a moment to go back over a number of the reading available on the subject to post a documentation entry in eZpedia. Please feel free to expand and add to the page! <i>http://ezpedia.org/wiki/en/ez/project_new_project_section_on_ez_no</i>
Cheers,
//kracker <i>mc chris - Pw_Om</i>
Member since: 2001.07.13 || http://ezpedia.se7enx.com/
|
|
Kristof Coomans
|
Sunday 10 December 2006 2:18:37 am
Hi Niklas I'll continue working on the projects section next week.
independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org
|
|
kracker (the)
|
Sunday 10 December 2006 3:02:41 am
<b>@Niklas Gunnäs</b> <i>While I agree with your end goals...</i> I think that the direction of your outcry would be best replicated to eZ systems.
They had the ez.no bug system before wiT, if you want that code
to be shared with the community (especially since it's been replaced by wiT)
you should ask eZ systems (say via email) directly. <i>I'm all for the goals but I don't think it's fair to add this to Kristof's project load alone.</i> If an existing software solution can not be found to base a solution upon it must then be created from scratch, which will be time consuming. The community could use more people stepping up and filling a need, now more than ever ... The new project section will be the foundation of a way to take a developer with an idea and turn it into a feature request with the code to implement the feature request very quickly. The forums will allow for alternate ways of providing for bug reporting, doc and discussion. It's far from great but it quickly becomes a matter of how far will you go to ensure the features you want get implemented .... In the end all constructs can be adapted, look at how comments become forums. There is more to be said for methodology rather than functionality. That said, I have spoken out for the sharing of ez.no code like the bug section. If I were you, I would ... open a dialog with eZ systems, see what they would require to share the code, who knows it might come down to the right price.
//kracker
<i>*shrugs*, file a bug, promote it, work for it, make it happen on your own. leave a trail for the next guy ...</i>
Member since: 2001.07.13 || http://ezpedia.se7enx.com/
|
|
Niklas Gunnäs
|
Monday 11 December 2006 6:40:49 am
@Kristof Thats nice to hear and sorry if my question sounded rude. You are doing a great work and I would like to say thanks for all your hard work with helping people and making contribution to the community. About the project section Did Paul Forsyth talk with vwt about design for the project section? or is it still open? @kracker I was thinking in the same direction. If ez is helping kristof with the project section maybe they can contribut there old bug tracker code. It may not been as advanced as wits bug tracker but it shure would work great for most users need. I have asked them before but at that time they was not intrested to share the code. Maybe the have change there mind when the old bug system not in use anymore. One can always hope :-) I had a strange fealing that the ez people already was reading my posts ;-) Hopefuly the do and get my view on including a free bug tracker :-) Best regards
|
|
Kristof Coomans
|
Monday 11 December 2006 7:39:06 am
Hi Niklas Your question didn't sound rude, it has been quiet for some weeks now about this subject so I understand that you're all curious to have some news. Concerning the relationship with eZ systems: actually it's the other way around, I'm going to help them with the projects section. I'll do the basic templating too, design will be integrated in ez.no. About the issue tracker: we'll see what the future brings...
independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org
|
|
Kristof Coomans
|
Wednesday 03 January 2007 9:41:44 am
I have some delay with my work related to the projects section because I have been ill during the Christmas vacation. Stay tuned!
independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org
|
|
Kristof Coomans
|
Saturday 17 February 2007 8:03:24 am
I wrote about the projects section on my blog today:
http://blog.coomanskristof.be/2007/02/17/ez-projects-status/ We're almost there... hang on!
independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org
|
|
Kristof Coomans
|
Wednesday 21 February 2007 4:14:51 am
There's a test install now on http://projects.ez.no Please read http://projects.ez.no/ez_projects/news/the_ez_projects_test_site_has_been_launched first.
independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org
|
|
Niklas Gunnäs
|
Friday 13 April 2007 1:02:21 am
Hi Kristof, Any news to share about ez projects development. Is there any way I could help so just tell me. Best regards Niklas
|
