Hi Andreas, all, Le 10/02/2014 22:38, Andreas Mantke a écrit : > Hi Cor, > > Am 10.02.2014 22:06, schrieb Cor Nouws: >> Andreas Mantke wrote (10-02-14 19:16) >> >>> I looked over your draft and get only a bit of your proposal, maybe >>> because a spreadsheet is not the best tool to draw a website structure. >> Nah - you must be kidding ;) >> > I'd prefer Draw or Impress for that, but everybody is using his/her > preferred tool ;-) >>> I try to summarize what I got from your draft: >>> >>> You want a home page (landing page) that has search box, a listing of >>> search results, the login, a link to information about installing >>> extensions, a link to a bugtracker and a link to an explanation of the >>> purpose of extensions (or a box with a teaser and a link to the long >>> explanation). >>> >>> Did I summarize that correct? >> Yes, that is OK, plus that I would like to have searches for Most >> recent, Most popular, and By category. > Should that be search forms or a button/link that trigger a search and > give back the result in the list field on the site? I figure out the latter. >> And the bugtracker may also info on how/where to report bugs .. > Hmm. A bugtracker on the site or the upcomming LibreOffice bugtracker?
For information, when there is bug reported on extension, we close it as not our bug, so may be it would be a better user experience to give the contact of the extension owner to report the issue. >> >>> But then I'm a bit lost. The next fields in your spreadsheet are further >>> pages? >>> Are they in a hierarchical order? >> OK, I clarified the sketch a bit. >> >> https://wiki.documentfoundation.org/File:ExtensionsSite_IdeasOnContent_CorNouws_20140210.ods >> >>> Do we want to create projects for the extensions? >> For a user that would not be interesting, I guess. Only from a technical >> POV that might matter? > Right. But without a structure the site will be a mess soon. >>> Should there be a release for an extension with information about the >>> LibreOffice version that it works with? >> Yes, see the page "New extension" though LibreOffice version is not >> mandatory IMO. > But it would be a value for users to know which version(s) of > LibreOffice the extension is working with. Thus I prefer to make that > mandatory. This would make it possible to search for extensions that run > with a specific version of LibreOffice. On the other hand it put a > burden on the author, because he had to add new versions of LibreOffice > later. Would it be possible to remove the warning about the fact that the extension has not been updated since xx time. Most of the time extensions are working from one version to another. >>> How many different extension files are posible for a release? >>> If there is some compiled stuff inside an extension it could run e.g. >>> only on Linux-i586 or -x64. >> Ah, interesting. Yes of course it's very good to take that onto >> consideration. Would it be needed to add a limit? >> Can't it be simple >> [ upload path ] [ for version |V] (list) [ for OS |V] (list) + >> >> where version and OS have 'all' too and that clicking + adds a new line >> and that at the end the author clicks [Add] or [Submit] ? > If the site uses an own content type for the file upload you could ad as > many files as you like. But if the contributor choose the files on the > release page itself there had to be a field for each file. Otherwise the > former file would be dropped once the contributor choose a new one. Cheers Sophie -- To unsubscribe e-mail to: website+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/website/ All messages sent to this list will be publicly archived and cannot be deleted
