Hi,
would anyone complain if I just push converted content from fedorahosted to the docs repo w/o review as long as there are no changes OR the changes are just alingnment of 1.15 design documents with the actual implementation?
As 1.15 is making its way to downstreams, there are people interested in what we've accomplished in this release and we should make sure the changes are documented.
For totally new content, I think we should have at least spot-check the docs during a review.
On (30/03/17 21:22), Jakub Hrozek wrote:
Hi,
would anyone complain if I just push converted content from fedorahosted to the docs repo w/o review as long as there are no changes OR the changes are just alingnment of 1.15 design documents with the actual implementation?
Design documents can be converted + release notes becasue they were not very structired. Automatic conversion of rest was not ideal and many parts were either missing or mis-formatted. I do not think it is the best idea to push everything.
As 1.15 is making its way to downstreams, there are people interested in what we've accomplished in this release and we should make sure the changes are documented.
+1
For totally new content, I think we should have at least spot-check the docs during a review.
Could you ellaborate? What do you mean by docs and which review?
Ls
On Fri, Mar 31, 2017 at 10:53:03AM +0200, Lukas Slebodnik wrote:
On (30/03/17 21:22), Jakub Hrozek wrote:
Hi,
would anyone complain if I just push converted content from fedorahosted to the docs repo w/o review as long as there are no changes OR the changes are just alingnment of 1.15 design documents with the actual implementation?
Design documents can be converted + release notes becasue they were not very structired. Automatic conversion of rest was not ideal and many parts were either missing or mis-formatted. I do not think it is the best idea to push everything.
I would like to manually convert the features for 1.15, maybe some very high profile ones for 1.14, but probably not. I don't think many people would be interested in old features.
I think the old feature pages can be just migrated using your conversion so that we don't waste time.
As 1.15 is making its way to downstreams, there are people interested in what we've accomplished in this release and we should make sure the changes are documented.
+1
For totally new content, I think we should have at least spot-check the docs during a review.
Could you ellaborate? What do you mean by docs and which review?
For example https://pagure.io/SSSD/docs/pull-request/5 or any new howto we write. I think before pushing, the doc submissions should be reviewed by another developer (design documents were already reviewed for a long time).
On (30/03/17 21:22), Jakub Hrozek wrote:
Hi,
would anyone complain if I just push converted content from fedorahosted to the docs repo w/o review as long as there are no changes OR the changes are just alingnment of 1.15 design documents with the actual implementation?
As 1.15 is making its way to downstreams, there are people interested in what we've accomplished in this release and we should make sure the changes are documented.
I've just realized one thing. Do we want to setup redirects from fedorahosted wiki to pagure?
https://fedorahosted.org/sssd/wiki/ -> https://docs.pagure.org/SSSD.sssd/
e.g. https://fedorahosted.org/sssd/wiki/DesignDocs/DBusUsersAndGroups -> https://docs.pagure.org/SSSD.sssd/DesignDocs/DBusUsersAndGroups.html
Because ATM directories have different names. https://docs.pagure.org/SSSD.sssd/design_pages/ DesignDocs vs. design_pages ...
LS
On Tue, Apr 18, 2017 at 06:35:53PM +0200, Lukas Slebodnik wrote:
On (30/03/17 21:22), Jakub Hrozek wrote:
Hi,
would anyone complain if I just push converted content from fedorahosted to the docs repo w/o review as long as there are no changes OR the changes are just alingnment of 1.15 design documents with the actual implementation?
As 1.15 is making its way to downstreams, there are people interested in what we've accomplished in this release and we should make sure the changes are documented.
I've just realized one thing. Do we want to setup redirects from fedorahosted wiki to pagure?
https://fedorahosted.org/sssd/wiki/ -> https://docs.pagure.org/SSSD.sssd/
e.g. https://fedorahosted.org/sssd/wiki/DesignDocs/DBusUsersAndGroups -> https://docs.pagure.org/SSSD.sssd/DesignDocs/DBusUsersAndGroups.html
Yes, but I guess we'll want to do this on a page-by-page basis. At least for the newer design pages we care about and pages like troubleshooting. I think it makes sense to name them nicely and ask for a redirect.
For older design pages (<1.14) I don't really care, we can just autogenerate them from the sqlite dump and use the same names so that they are easier to set up redirects (at least the "leaf" of the name)
Because ATM directories have different names. https://docs.pagure.org/SSSD.sssd/design_pages/ DesignDocs vs. design_pages
sssd-devel@lists.fedorahosted.org