Alan Burlison wrote: > Hi Paul, > > >> I've added some new wiki requirements to the genunix wiki: >> >> http://www.genunix.org/wiki/index.php/OpenSolarisWiki#Paul.27s_List_Additions >> >> I'm not sure how this page is being updated: >> >> http://www.opensolaris.org/os/project/website/wiki_requirements/ >> > > Sorry to be a pain, but could everyone post comments etc to > website-discuss rather than updating the genunix page, or any of the > other similar ones? I've asked Chris to coordinate the requirements > gathering, and he's already melded together the existing mail & wiki > pages that have covered this topic in the past. It's going to get > confusing if those pages are still being updated. If you post stuff > here, Chris can collate it all and update the wiki_requirements page. > > Chris, can you pick up Paul's additions and add them to the page? > > Thanks! >
For the benefit of the list, Paul's additions are: -Ability to provide comments on pages (must have). -Ability to export multiple pages to PDF (nice to have) -Wiki integrated into the OpenSolaris site structure (must have); I would like to see the Project and Community sites be their own wikis. -Ability to set up roles and permissions (must have) I've added 'Ability to provide comments on pages' as a conditional requirement (C19) because not all wiki technologies make the distinction between commenting and editing (one might not have edit privileges, but might still be able to comment). So, yes, the ability to make comments should be an explicit requirement. The ability to export pages as PDF is already noted as an optional requirement (now O21). Integration into the OpenSolaris site structure is, I think, implicit. The corollary of Project and Community sites being their own wikis I think is addressed by the conditional requirement for name space support, if I understand Paul's point correctly. Roles and permissions are 'must have' requirements, but are addressed by the E2 essential requirement for pluggable authentication. http://auth.opensolaris.org references the authentication architecture, but the E2 requirement does not explain the interaction between the auth app and the wiki software, that is, that the auth application will have role information which must be mapped to the wiki software's notion of roles and hence permissions. I'll remedy that. Thanks Paul, and please correct me if I have misinterpreted your requirements. Chris _______________________________________________ website-discuss mailing list [email protected]
