On 8/5/07, David Chisnall <[EMAIL PROTECTED]> wrote: > > On 5 Aug 2007, at 17:22, Yen-Ju Chen wrote: > > > On 8/5/07, David Chisnall <[EMAIL PROTECTED]> wrote: > >> On 4 Aug 2007, at 03:22, Jesse Ross wrote: > > > > Well, you don't really need to use a lot of HTML for blog. > > Right. I mainly use headings, paragraphs and occasionally some > markup for code and quotes. > > > The purpose of blog is easy to publish. > > I agree. I'm not convinced Blogger fulfils this. > > > I do agree that the comments are not notified. > > But on the other hand, it is easier to discuss on maillist or SILC. > > So I rather not to use blog for serious discussion. > > It is more like a bulletin board for me. > > I think having a bad comments system is worse than having no comments > system. If people leave a comment with a question, then they should > expect a reply. We don't have a good way of doing this. One option > might be to support cross-posting between the blog and a mailing > list, and use the archives of the mailing list instead of comments. > > > And most people probably read RSS, not even the blog web site. > > When I read RSS, I see the heading in a summary view, click on the > link, and go to the site. > > > So I would say these are very minor issues. > > I feel it is more important to have a blog easy to manage. > > And blogger use gmail account, which I believe most of us > > has one already. > > I had to create a Google account for the Summer of Code. I only use > it for that and posting on the blog. Until the SoC started, I didn't > have a Google account. > > > I can image the documentation change much less than code. > > Well, I'd like to be as OCD about this as Theo de Raadt and say no > code commits without corresponding documentation update. More > realistically, we should at least try to keep the documentation up to > date with the code, so any interface changes will require updates to > the documentation.
But I see no need to publish documentation when the API is under developement. The way I see documentation is just like making release of the tarball. So we only need to do so when preparing the next relelease by generating the documentation and uploading onto svn. As for using download for documentation than svn, I feel it is weird to use "http://download.gna.org/etoile/"; for that. And that area is not easy to modify. You have to download the document, modify it, then upload again unless rsync can make it easier, which I don't know yet. That area also hosts the live CD, which are really big. I rather not to have a copy of all of them because I need to use rsync. Yen-Ju > > > So I don't see the need to regenerate it whenever code changes. > > The download area has permission issues. > > For example, yesterday I tried to update the dependencies > > directory, but directory was created by Quentin, > > so I have no permission to use rsync or even sftp with it. > > You can fix this with a sensible umask or an explicit chmod. The > group for uploads is set automatically to etoile, so as long as > uploaded files have permissions set to 664 or similar, it will work. > I uploaded an etoile.html test file there. Check if you can modify it. > > > It is not a ideal place for collaborative work. > > I still think GNA web space is a good place for documentation, > > where we can upload documentation manually. > > I think it will be tricky to do this via SVN without breaking > things. The documentation make routine will generate a directory > hierarchy, which just wants to be mirrored in the repository. Doing > this kind of thing with SVN is non-trivial. > > > Since it also support SSI, I think it would be good as > > our front page, too. > > Definitely agree. > > > I agree here mostly to use GNA space. > > I also want to mention that I don't really like to allow users > > put comments everywhere (blog, wiki, etc). > > It is really hard to find them all and reply back. > > I rather pool all the discussion on maillist and SILC. > > To me, blog and wiki are just a place for publish, > > not discussion. > > Yup. If there's a discussion area anywhere, I want it to notify me > when someone posts something. I don't want to have to keep polling > various areas of the web site. > > David > > _______________________________________________ > Etoile-discuss mailing list > [email protected] > https://mail.gna.org/listinfo/etoile-discuss > _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
