On Mon, May 16, 2016 at 12:20 PM, Daniel Ruggeri <[email protected]> wrote: > On 5/16/2016 1:35 PM, Mike Jumper wrote: >> Hey all, >> >> gitpubsub has finally been enabled, and the Apache Guacamole website >> is now publicly visible: >> >> http://guacamole.incubator.apache.org/ > > Well done on the simple but useful description of the project right on > the main page! This is good. > > On 5/16/2016 1:45 PM, Mike Jumper wrote: >> That should already be the case (see >> https://github.com/apache/incubator-guacamole-manual/blob/master/src/gug.xml#L14-L26). >> The only reason the old copyright is still visible there is that it's >> a snapshot of the pre-Apache 0.9.9 release of the Guacamole Manual. >> >> On Mon, May 16, 2016 at 11:39 AM, James Muehlner >> <[email protected]> wrote: >>> > Huzzah! Looks good to me for the most part. >>> > >>> > Are we going to transfer copyright for the manual to apache? >>> > http://guacamole.incubator.apache.org/doc/gug/ >>> > >>> > James > Is a release upcoming soon enough or is it otherwise not complicated to > regen the docs? > >
I'd be more in favor of updating the docs along with a true post-Apache "-incubating" release. The docs have historically been tied to the release, and while correcting problems in the docs without a release is definitely OK, I don't think they should be updated to reflect changes which are not present in the latest release, and the latest release is pre-Apache (0.9.9). Beyond that, it's not overly complicated, no. It's written in Docbook, has its own Makefile, and is contained within its own git repository (with README documenting the build): https://github.com/apache/incubator-guacamole-manual Speaking of which ... the READMEs of just about all repositories now need to be updated to reflect the newly-deployed website and the migration to Apache's JIRA. > > Also, I've been beaten into submission... erm, I mean... TRAINED to look > for trademarks. I haven't dug through the archives yet to know if this > was discussed, but registration ([email protected]) and including > the TM in prominent places on the site (particularly the home page and > downloads pages) are things to keep in mind as goals once graduation > from Incubator occurs. > If we don't need to wait for TLP status to request registration of "Guacamole" as an ASF trademark, I'd be glad to get that process going. Is this the case? Logos as well? We currently have three: 1) The detailed full-color guac bowl (currently used as the page favicon) 2) The low-detail tri-color guac bowl (the logo used on the homepage, within the web application, and just about everywhere else) 3) A monochrome version of the same low-detail logo > As a final note (more of a nit than anything), I often find projects > missing a description of the "flow" once a piece of code is contributed > or a bug is submitted. Should they see feedback? When they get feedback, > will it be in a ticket? on the dev list? What's the process once it's > committed to trunk to make it into a release, etc? > The closest thing we have thus far are the contribution guidelines and the help/support page: http://guacamole.incubator.apache.org/open-source/ http://guacamole.incubator.apache.org/support/ Based on the conversation regarding the recent proposed contribution of a Portuguese translation [1], it sounds like the guidelines above may be partially incorrect, as they note CLAs as a requirement. Anything you see in the above pages that could use more description of "flow"? - Mike [1] https://lists.apache.org/thread.html/Zi5qs1o7hxkirf7
