I think that xoopscube.sourceforge.net should have "download center" that handles BASEs, modules, themes and code snippets (including preload), because it's difficult that each support site keeps download center and manages it. Our policy is compact. Our man power is very low. And developers in the project can not welcome end-users as web master. Therefore, our Download Center will need to have relations with each support site.
But, we should not wait "Manifesto" discussion. And we need experiences as an examination.
* Make simple download center Spring.
* After "Manifesto" discussion, we will delete all items and will re-open new download center.
* Developers in the project manages data.
What do you think about that?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We need to create a Wiki page "How to upload to Download Center"
Syntax to define a namespace , package_name_country_version
whatever (i keep in mind that we all adopt definetely utf8)
Need also some more categories: Modules, Themes, Preloads
something like frameworks (ajax, css, wysiwyg editors and
anyother php framework used by module developers)
Because we didn't decide the manifesto format, I didn't go forward for the next step on this task. The Download Center Project will be restarted next month.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I think that xoopscube.sourceforge.net should have "download center" that handles BASEs, modules, themes and code snippets (including preload), because it's difficult that each support site keeps download center and manages it. Our policy is compact. Our man power is very low. And developers in the project can not welcome end-users as web master. Therefore, our Download Center will need to have relations with each support site.
Manifesto format gives effect to this plan.
https://sourceforge.net/forum/forum.php?thread_id=1931794&forum_id=537172
But, we should not wait "Manifesto" discussion. And we need experiences as an examination.
* Make simple download center Spring.
* After "Manifesto" discussion, we will delete all items and will re-open new download center.
* Developers in the project manages data.
What do you think about that?
We need to create a Wiki page "How to upload to Download Center"
Syntax to define a namespace , package_name_country_version
whatever (i keep in mind that we all adopt definetely utf8)
Need also some more categories: Modules, Themes, Preloads
something like frameworks (ajax, css, wysiwyg editors and
anyother php framework used by module developers)
To make support sites management easier,
webmasters can create a block
or page using Project RSS Feeds: xoopscube
https://sourceforge.net/export/rss2_project.php?group_id=159211
Our team man number can be lower but each man a lot more powerful^^
Hi,
Is there someone in charge of this task?
Can some categories be created?
Note: I'm adding a request to tracker !
Because we didn't decide the manifesto format, I didn't go forward for the next step on this task. The Download Center Project will be restarted next month.
Gijoe post a solution to complete sf.net rss
So, we have now sf.net forums feeds
Isn't that great ^^
http://sourceforge.net/forum/forum.php?thread_id=2023469&forum_id=537171