Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2010-02

Part II of Reconstructing Lazarus Website 2: the content

13 messages · 7 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Bee Jay

Hi all,

While the discussion about the page layout is still hot, let's discuss the true problem of all: THE REAL CONTENT! :)

As you may already know, my proposal already have a content structure as shown in the footer bar. Now, I ask for your help to fill the content for them. First, let me describe what the content it should have, as in my thought.

- Overview: summary with brief description of all contents, from Learn to Download.
- F.A.Q: list of commonly asked questions, especially from new comers.
- Learn: summary with enough description of how to use Lazarus for the first time, from where to get the installer, how to install it, open a sample project, run and debug it, until deploy the executable.
- Features: list of key features and advantages using Lazarus as a development tool.
- Component (or Libraries in FreePascal section): list of available components (LCL) that can be used in Lazarus, including from third parties (only the very useful ones).
- Documentations: list of official release documentation e.g. release notes, installation guide, user manual, etc. that can be downloaded (pdf?) or viewed online (wiki? html?).
- Roadmap: list of plan for the next release(s).
- Download: list of download links for binary installer, devel snapshots, mirrors, etc.

Remember that FPC and Lazarus each has its own section for the above pages.

Let's get them straight and complete, before we discuss the other sections. Please elaborate your ideas and proposal. Thank you.

-Bee- ...making buzzes at http://twitter.com/beezing ...writing stories at http://beeography.wordpress.com

Reply by email

Paul Ishenin
to Bee Jay
Bee Jay wrote
- Roadmap: list of plan for the next release(s).

This will be very hard to get. After every release I ask other developers of what they plan and I get no much info. For example for 0.9.30 we have only the next items:
http://wiki.lazarus.freepascal.org/Lazarus_0.9.30_todo and nobody guaranty that any item will be really implemented for 0.9.30

You can look that only about 50% of tasks are usually implemented for release. Previus roadmaps can be found here:
http://wiki.lazarus.freepascal.org/Lazarus_Development_Process

Best regards,
Paul Ishenin.

Reply by email

Martin
to Paul Ishenin
Paul Ishenin wrote 12 lines
05.02.2010 0:46, Bee Jay wrote: > - Roadmap: list of plan for the next release(s). This will be very hard to get. After every release I ask other developers of what they plan and I get no much info. For example for 0.9.30 we have only the next items: http://wiki.lazarus.freepascal.org/Lazarus_0.9.30_todo and nobody guaranty that any item will be really implemented for 0.9.30 You can look that only about 50% of tasks are usually implemented for release. Previus roadmaps can be found here: http://wiki.lazarus.freepascal.org/Lazarus_Development_Process

Maybe we should decouple the Roadmap from Versions?

Just have a list of features that are planed or requested (or rejected, if so). This could reduce duplicate feature requests.

Each feature could have a status like:
- in progress
- assigned
- contributor needed
- ...

Martin

Reply by email

Paul Ishenin
to Felipe Monteiro de Carvalho
Felipe Monteiro de Carvalho wrote 7 lines
I usually just put what I did directly here: http://wiki.lazarus.freepascal.org/Lazarus_0.9.30_release_notes Development can often be very expontaneous. It's not like you plan to fix something, but while developing something or fixing a bug report you need to fix it and then it gets done ...

I think roadmap is not about fixing bugs but about feature planing.

Best regards,
Paul Ishenin.

Reply by email

Paul Ishenin
to Martin: Maybe we should decouple the Roadmap from Versions? Just have a list of features that are…
Martin wrote 10 lines
Maybe we should decouple the Roadmap from Versions? Just have a list of features that are planed or requested (or rejected, if so). This could reduce duplicate feature requests. Each feature could have a status like: - in progress - assigned - contributor needed - ...

Bounty (http://wiki.lazarus.freepascal.org/Bounties) page? Only in progress status is not there.

Best regards,
Paul Ishenin.

Reply by email

Bee Jay
to Paul Ishenin: This will be very hard to get. After every release I ask other developers of what they…
Show quoted text 5 lines
This will be very hard to get. After every release I ask other developers of what they plan and I get no much info. For example for 0.9.30 we have only the next items: http://wiki.lazarus.freepascal.org/Lazarus_0.9.30_todo and nobody guaranty that any item will be really implemented for 0.9.30

Website isn't made of a rock stone. If the contents have to change for some reasons, then be it.

There are other things that also need to be considered, let's think about them as well. Any proposal for other contents? TIA.

-Bee- ...making buzzes at http://twitter.com/beezing ...writing stories at http://beeography.wordpress.com

Reply by email

Alexander Klenin
to Paul Ishenin: Bounty (http://wiki.lazarus.freepascal.org/Bounties) page? Only in progress status is not…
Paul Ishenin wrote 15 lines
05.02.2010 8:28, Martin wrote: > > Maybe we should decouple the Roadmap from Versions? > > Just have a list of features that are planed or requested (or rejected, > if so). This could reduce duplicate feature requests. > > Each feature could have a status like: > - in progress > - assigned > - contributor needed > - ... Bounty (http://wiki.lazarus.freepascal.org/Bounties) page? Only in progress status is not there.

Is not this what the bug tracker is for?

Alexander S. Klenin

Reply by email

Graeme Geldenhuys
to Alexander Klenin
Alexander Klenin wrote 5 lines
> > Bounty (http://wiki.lazarus.freepascal.org/Bounties) page? Only in progress > status is not there. Is not this what the bug tracker is for?

Apparently not. Bug tracker is only for bugs you think you know somebody is actually going to fix. Anything else should go into Bounty page. This is what I was told, so don't shoot the messenger. ;-)

Regards, - Graeme - _______________________________________________ fpGUI - a cross-platform Free Pascal GUI toolkit http://opensoft.homeip.net/fpgui/

Reply by email

Alexander Klenin
to Graeme Geldenhuys
Graeme Geldenhuys wrote 6 lines
On 7 February 2010 10:29, Alexander Klenin wrote: > Is not this what the bug tracker is for? Apparently not. Bug tracker is only for bugs you think you know somebody is actually going to fix. Anything else should go into Bounty page. This is what I was told, so don't shoot the messenger. ;-)

Hm. How can I (or anybody) know that unless I am going to fix the bug myself? I think that Bounty page is for bugs somebody is willing to pay for fixing, and bug tracker is for all the other bugs.

Alexander S. Klenin

Reply by email

Vincent Snijders
to Graeme Geldenhuys: Apparently not. Bug tracker is only for bugs you think you know somebody is actually…
Graeme Geldenhuys wrote 9 lines
On 7 February 2010 10:29, Alexander Klenin wrote: >> Bounty (http://wiki.lazarus.freepascal.org/Bounties) page? Only in progress >> status is not there. > Is not this what the bug tracker is for? Apparently not. Bug tracker is only for bugs you think you know somebody is actually going to fix. Anything else should go into Bounty page. This is what I was told, so don't shoot the messenger. ;-)

I am not sure who told you that, but then I feel I have to correct him and you.

What you wrote it true for new features, to prevent the bug tracker from flooding with everybody's wildest ideas and feature requests. This absolutely not true for bugs, things that are not working as designed.

Vincent

Reply by email

Vincent Snijders
to Alexander Klenin: Is not this what the bug tracker is for? Alexander S. Klenin
Alexander Klenin wrote 17 lines
On Fri, Feb 5, 2010 at 10:00, Paul Ishenin wrote: > 05.02.2010 8:28, Martin wrote: >> Maybe we should decouple the Roadmap from Versions? >> >> Just have a list of features that are planed or requested (or rejected, >> if so). This could reduce duplicate feature requests. >> >> Each feature could have a status like: >> - in progress >> - assigned >> - contributor needed >> - ... > Bounty (http://wiki.lazarus.freepascal.org/Bounties) page? Only in progress > status is not there. Is not this what the bug tracker is for?

Bug tracker is for bugs, and status is noted there.

If you want to pay for getting a particular bug fixed or a feature implemented, then you can add it to the bounty page.

Vincent

Reply by email