Re: [leaf-devel] LEAF history
On 07/21/2013 11:21 AM, KP Kirchdoerfer wrote: > Am 21.07.2013 19:52, schrieb Mike Noyes: >> On 07/21/2013 10:21 AM, KP Kirchdoerfer wrote: >>> Hi, >>> >>> Am 21.07.2013 17:09, schrieb Andrew: Hi all. It seems like LEAF history task becomes lost somewhere into mailing list archives... I think that it'll be good for project if it'll be written (at least early stages and main releases with short benefits description). >>> >>> Indeed the idea was lost in the archives. >>> And with the updates for 5.0.1-beta1 I think updating packages has >>> almost been for the time being, so there should be some time to write a >>> draft for the history (good time to reflect history after Bering-uClibc >>> hit the 100.000 downloads milestone last week). >>> Anyway, my concerns are still, where it should be published. >>> The current pages are outdated, and maintenance is difficult, if not >>> impossible (adding packages for v5 does not work etc..) >>> So moving to a new CMS is IMHO urgent. >> >> Everyone, >> The website is my fault. I can extract the content from the database, >> and convert it to html. I propose we import it into Mediawiki as a >> temporary measure. I'll then archive the website, place it in the FRS, >> and delete it from the shell. I'll then make Mediawiki our project website. >> >> Comments? > > There are certainly a few questions we have to decide first: > 1) what about roles/access > 2) what about LEAF versions beyond Bering-uClibc (even if they are > historical)? > 3) integration with SF Allura > 4) integration of packages page with links to git repo, where a user can > download seperate packages. > > To summarize - I do not like pages that looks like a wiki - and though > David did a very good job moving our docs from docbook-based webpages to > wiki, the main entry should be something more appealing than the "wiki > look". > That's the reasons, I've liked your idea to use drupal etc.. KP, Understood. > But maybe you can provide a proposal of Mediawiki for our project > website, that will proof me wrong. This is a temporary measure. We need to get the content out of phpWebsite; and placing it in the wiki will allow us to organize, prune, etc. the content before placing it in a new CMS. -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/113364780158082152468 -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LEAF history
Am 21.07.2013 19:52, schrieb Mike Noyes: > On 07/21/2013 10:21 AM, KP Kirchdoerfer wrote: >> Hi, >> >> Am 21.07.2013 17:09, schrieb Andrew: >>> Hi all. >>> It seems like LEAF history task becomes lost somewhere into mailing list >>> archives... I think that it'll be good for project if it'll be written >>> (at least early stages and main releases with short benefits description). >> >> Indeed the idea was lost in the archives. >> And with the updates for 5.0.1-beta1 I think updating packages has >> almost been for the time being, so there should be some time to write a >> draft for the history (good time to reflect history after Bering-uClibc >> hit the 100.000 downloads milestone last week). >> Anyway, my concerns are still, where it should be published. >> The current pages are outdated, and maintenance is difficult, if not >> impossible (adding packages for v5 does not work etc..) >> So moving to a new CMS is IMHO urgent. > > Everyone, > The website is my fault. I can extract the content from the database, > and convert it to html. I propose we import it into Mediawiki as a > temporary measure. I'll then archive the website, place it in the FRS, > and delete it from the shell. I'll then make Mediawiki our project website. > > Comments? There are certainly a few questions we have to decide first: 1) what about roles/access 2) what about LEAF versions beyond Bering-uClibc (even if they are historical)? 3) integration with SF Allura 4) integration of packages page with links to git repo, where a user can download seperate packages. To summarize - I do not like pages that looks like a wiki - and though David did a very good job moving our docs from docbook-based webpages to wiki, the main entry should be something more appealing than the "wiki look". That's the reasons, I've liked your idea to use drupal etc.. But maybe you can provide a proposal of Mediawiki for our project website, that will proof me wrong. kp -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LEAF history
On 07/21/2013 10:21 AM, KP Kirchdoerfer wrote: > Hi, > > Am 21.07.2013 17:09, schrieb Andrew: >> Hi all. >> It seems like LEAF history task becomes lost somewhere into mailing list >> archives... I think that it'll be good for project if it'll be written >> (at least early stages and main releases with short benefits description). > > Indeed the idea was lost in the archives. > And with the updates for 5.0.1-beta1 I think updating packages has > almost been for the time being, so there should be some time to write a > draft for the history (good time to reflect history after Bering-uClibc > hit the 100.000 downloads milestone last week). > Anyway, my concerns are still, where it should be published. > The current pages are outdated, and maintenance is difficult, if not > impossible (adding packages for v5 does not work etc..) > So moving to a new CMS is IMHO urgent. Everyone, The website is my fault. I can extract the content from the database, and convert it to html. I propose we import it into Mediawiki as a temporary measure. I'll then archive the website, place it in the FRS, and delete it from the shell. I'll then make Mediawiki our project website. Comments? -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/113364780158082152468 -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LEAF history
Hi, Am 21.07.2013 17:09, schrieb Andrew: > Hi all. > It seems like LEAF history task becomes lost somewhere into mailing list > archives... I think that it'll be good for project if it'll be written > (at least early stages and main releases with short benefits description). Indeed the idea was lost in the archives. And with the updates for 5.0.1-beta1 I think updating packages has almost been for the time being, so there should be some time to write a draft for the history (good time to reflect history after Bering-uClibc hit the 100.000 downloads milestone last week). Anyway, my concerns are still, where it should be published. The current pages are outdated, and maintenance is difficult, if not impossible (adding packages for v5 does not work etc..) So moving to a new CMS is IMHO urgent. > P.S. It'll be good also to update news on main page - there is still > 4.3.3 release on top Yes, it does not work at all for the main page, updating Bering-uClibc pages is painful - that's why the latest annoucements has been done in the "blog" (http://sourceforge.net/p/leaf/blog/?source=navbar) as a "workaround". Mike, any chance we'll have an up-to-date CMS soon? We really need a replacement for the current CMS. and I think there will be enough decisions to make to start ASAP. kp > 12.09.2012 19:29, Mike Noyes пишет: >> On 09/11/2012 11:25 AM, KP Kirchdoerfer wrote: >> -snip- >>> But first I'd like to see, if the current webpages are moved to a newer >>> CMS. What about this task Mike? >> KP, >> I'm still waiting on SF Staff to update the software on the project web >> farm, and implement openid. >> >> http://sourceforge.net/p/forge/community-docs/Hosted%20Apps%20Retirement/ >> >> - Timeline - >> OpenID authentication to SourceForge accountsIn-progress, target for >> completion in July >> Updates to Project web to support apps Planned for August/September >> > > > -- > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > > ___ > leaf-devel mailing list > leaf-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-devel > -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] LEAF history
Hi all. It seems like LEAF history task becomes lost somewhere into mailing list archives... I think that it'll be good for project if it'll be written (at least early stages and main releases with short benefits description). P.S. It'll be good also to update news on main page - there is still 4.3.3 release on top 12.09.2012 19:29, Mike Noyes пишет: > On 09/11/2012 11:25 AM, KP Kirchdoerfer wrote: > -snip- >> But first I'd like to see, if the current webpages are moved to a newer >> CMS. What about this task Mike? > KP, > I'm still waiting on SF Staff to update the software on the project web > farm, and implement openid. > > http://sourceforge.net/p/forge/community-docs/Hosted%20Apps%20Retirement/ > > - Timeline - > OpenID authentication to SourceForge accounts In-progress, target for > completion in July > Updates to Project web to support appsPlanned for August/September > -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
