-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/24/2010 09:17 PM, Chris Curran wrote: > On 06/24/2010 11:09 PM, Justin Clift wrote: >> On 06/24/2010 10:07 PM, Eric "Sparks" Christensen wrote: >> <snip> >> >>> Things change and we need to be flexible with that but if we aren't >>> giving our readers a chance to properly review our new guides then we >>> aren't getting the feedback we need. If we aren't going to fix bugs >>> then... well, I'm going to fix my bugs. >>> >> My feeling is it would be beneficial to have the unstable development >> docs publicly viewable. Even if that means just the en-US versions, and >> not the translated versions. Something along the lines of: >> >> http://docs-devel.fedoraproject.org >> (that's not a real site) >> >> Having some kind of script triggered when a git commit is performed on a >> doc, that then uses publican to build the updated version, and publish >> it if successful. >> >> For now, I'm just manually generate the VG doc myself and publishing it >> to my personal fedorapeople.org space. Not optimal, but it works. >> >> There is a "Fedora Draft Documentation" heading on docs.fp.o, and I kind >> of wonder if that's maybe an alternative place we could put development >> docs stuff. It might get kind of crowded though, when we consider how >> many different branches of docs there would be. ;) >> >> Regards and best wishes, >> >> Justin Clift >> >> > I 100% agree with unstable public branches. Quick fixes are important > and what fedora is about. We need to be as agile as possible to stay up > to date with changing features. Realistically, the stable branch is not > going to be up to date for an entire fedora release (too much change). > > Translators need stability. We can and should provide that for them. We > can do both by publishing master and stable releases. That means incorrect information will be out in the wild. There should be a single version of every guide published and that single guide should be correct as far as we know it to be. > > Chris - --Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJMJJ0GAAoJEDbiLlqcYamxhDUP/RET1hmg21W+EGXonAdy6g+p O6bNLalC+QgbJ4+0l56Hl6BEhAXFQoOw9I55CDdOZNhG5e9miTRAEr0sKhHIPbpt X+ahjj4BQ26kMhkeduXc8Z3WFchif8Zcxrf1Bk23i7opWTU05ddNO6EOTjSdo12J SG+4HnRrz+TbRB/izJ6gl4mJ5brmaTFhmXp9OgymXnB9sk+P8RZlfkKla2skiI1A nq9KAgts0i5la3E4ousOg8VElLUi+4nl7OSMWQvnn1BH5myNx7xfyI0zXwKKOsZo JRON86wn1+IFCok/T7ezIm6Oy0Xsz8xg0aU41hI6Pyp9jxfA4wdCuQ7YdEeUzHbc tqs2Sxd5GPPyY4D3o3qT2fiQoAZiNWMkbPYUO88+WUjMGl0+RR7bXbNcGKWtRpT0 GsEg570hnEpnaO080GCrph+skC5E9VA1brSkyHGY/d2CymhuwxSTberbNw5bky2i yVADHQmL1s2TOSiPeUly+8Gn3o2XakXX8J9kM2XgEJj0ArbrBcQEAGQxKOt20S3c WaXMOlb61fHHVyt/K0sBzJxUTRQGmFhSyU8tHK3iYdW5+PQMmftpKzoyEqID160W 6BGfm/SEJAK8hLhODT43l+2n+oTrXYsrLuIWgyfKJSl0RYPvxR52cKJnhADyPiAB z2ofOgWUjolQCqWhnh24 =xM8g -----END PGP SIGNATURE----- -- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
