If the libvirt team wants to take responsibility for maintenance of these documents, and you as the writer would prefer to maintain them in the libvirt context, I don't see a problem with moving the repo there.
That said, I don't want to be in a position where we publish something at docs.fp.o that Fedora Docs writers cannot maintain, so if 'upstream' git moves there, we won't publish here.
That said, I don't want to be in a position where we publish something at docs.fp.o that Fedora Docs writers cannot maintain, so if 'upstream' git moves there, we won't publish here.
By first impulse kinda mirrors the conversation we had last week; the work is permissively licensed, if someone wants to use it, they can. If it stays in fedorahosted, there the libvirt team is welcome to maintain a 'fork' ( in the most positive possible sense of the word ). Merge workflow with multiple remotes isn't that bad, and if we really want to do pull request style collaboration, we can put it on pagure.
So, I have lots of thoughts - anyone else?
-- Pete
(PS - I'm top posting because of the precedent. It's uncomfortable :P)
On Wed, Aug 26, 2015 at 9:17 AM, David Ashley <w.david.ashley@xxxxxxxxx> wrote:
All -
Please read the attached email from the libvirt team.
So the question the libvirt team propose is where is the best place to host my document? They make a good point but I feel obligated to ensure the the Fedora Docs team come to a consensus about this question. I can work with it either way.
W. David Ashley
Fedora Docs Team
-------- Forwarded Message --------
Subject: Re: [libvirt] Libvirt Application Development Guide Using Python is now complete Date: Wed, 26 Aug 2015 11:37:14 +0100 From: Daniel P. Berrange <berrange@xxxxxxxxxx> Reply-To: Daniel P. Berrange <berrange@xxxxxxxxxx> To: David Ashley <w.david.ashley@xxxxxxxxx> CC: libvir-list@xxxxxxxxxx
On Tue, Aug 25, 2015 at 08:47:37AM -0500, David Ashley wrote: > All - > > I have finished work on the "Libvirt Application Development Guide Using > Python" book for the Fedora Docs Team. It is currently under review before > being published. > > I have confirmed that I can offer the guide back the the libvirt team for > their own use. The guide currently resides in a git repository and can be > obtained with > > git clone git://git.fedorahosted.org/git/docs/libvirt_application_development_guide_using_python.git > > > Please let me know if you publish the guide as I would like to keep track of > all the publishers so I can notify them about future updates. How do you want to manage this doc going forward. I'd personally have a preference for hosting it on the primary libvirt git server, rather than on Fedora hosted, so it is in the same place as all the other libvirt related repositories. We'd of course give you direct ability to push updates to the GIT repo in that case. Is there any workflow reason why you would need it to continue to be hosted on Fedora ? We'd also likely set up a job to automatically build it and publish HTML + PDFs on libvirt.org Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
--
docs mailing list
docs@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/docs
-- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
