Re: HIG migration
On Tue, Mar 30, 2021 at 2:26 AM Allan Day wrote: > Sriram Ramkrishna wrote: > ... > > I"m seeing more of this going forward - migration to gitlab pages. This > is great - but at some point we'll need to figure out how all this fits > together coherently. > > Good question. > > We have a current GSoD proposal that will look at auditing the wiki.gnome.org and then work on a proposal for documentation for GNOME for the dynamic content although not the api docs. There are puzzles to deal with it - for instance we've found that many get started working on GNOME code through extensions and do it without proper content. > I assume you will update the developer.gnome.org web pages and any other > housekeeping or is that going to be up to engagement/docs teams? Don't want > to assume :) > > My impression from reading Emmanuele's blog [1] is that the current > incarnation of developer.gnome.org (ie. based on library-web) is going > away, and that API docs will be generated using Sphinx in the future. > Fair enough - but I assume there must be some pointer that will need to be added. But if you migrate before the above happens then we should probably update the links. IMHO we should sunset developer.gnome.org as quickly as possible as it is full of GNOME3/GTK3 isms. > The design team is likely to use something Sphinx-like, with a > customised theme. That theme could be used by other GNOME projects to > give our docs a consistent look. We could also potentially investigate > common navigation elements, like a home button that takes you to > developer.gnome.org. > We also need to integrate https://gjs.guide/ which is another entry point into the GNOME developer-verse. > Regarding developer.gnome.org itself, I think we could potentially do > a new static home page which links off to each of the independent > Sphinx-generated docs sites. This would need to be manually updated to > add new content, but that's probably a good thing. > That makes sense to me. Best, sri > Allan > -- > [1] https://www.bassi.io/articles/2021/03/17/more-documentation-changes/ > ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: HIG migration
I"m seeing more of this going forward - migration to gitlab pages. This is great - but at some point we'll need to figure out how all this fits together coherently. I assume you will update the developer.gnome.org web pages and any other housekeeping or is that going to be up to engagement/docs teams? Don't want to assume :) sri On Mon, Mar 29, 2021 at 9:27 AM Allan Day wrote: > Hi all, > > This is a heads up that the design team is planning to migrate the HIG > from its current location in gnome-devel-docs to a repo in our team > space. We're planning on using Mkdoc or Sphinx for tooling, and Gitlab > pages for hosting. > > Cheers, > > Allan > ___ > gnome-doc-list mailing list > gnome-doc-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-doc-list > ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Google Summer of Docs proposal 2021
On Tue, Mar 16, 2021 at 11:02 AM Shaun McCance wrote: > On Mon, 2021-03-15 at 08:11 -0700, Sriram Ramkrishna wrote: > > Hey folks! > > I'm working on a GSoD for this year and I've outlined the proposal. I just > wanted to give you all a heads up. I'm mostly focusing on our wiki and > looking to remove everything updated, and update the ones that are still > valid. But we will also use that experience to build a better onboarding > experience by building a more supportable project documentation setup that > can be managed for the future. > > If you have any thoughts, questions, or comments that would be > appreciated. Here is the current proposal. > > https://etherpad.gnome.org/p/gsod-2021-proposal > > Thanks so much! > > > Thanks for taking point on this, Sri. I don't have the bandwidth to mentor > this time around, but I can help out with some stuff. > > Awesome - I'll keep that in mind but also set it up in a way that is cognizant of your time commitment. :) It's worth noting that I started an audit for things related to the > documentation team (not necessarily user or developer documentation per se): > > https://gitlab.gnome.org/Teams/documentation/initiatives/-/issues/1 > > I'd appreciate if we could keep that issue up to date on any pages listed > there. > Oh that's lovely - let me see if I can integrate that into the description so that we can give it some attention. Cheers, sri > Thanks, > Shaun > > ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Google Summer of Docs proposal 2021
On Mon, Mar 15, 2021 at 9:47 AM Andre Klapper wrote: > Hi, > > thanks for the quick reply. Comments inline. > > On Mon, 2021-03-15 at 09:35 -0700, Sriram Ramkrishna wrote: > > On Mon, Mar 15, 2021 at 9:08 AM Andre Klapper wrote: > > > On Mon, 2021-03-15 at 08:11 -0700, Sriram Ramkrishna wrote: > > > > I'm working on a GSoD for this year and I've outlined the proposal. > > > I > > > > just wanted to give you all a heads up. I'm mostly focusing on our > > > wiki > > > > and looking to remove everything updated, and update the ones that > > > are > > > > still valid. But we will also use that experience to build a better > > > > onboarding experience by building a more supportable project > > > > documentation setup that can be managed for the future. > > > > > > > > If you have any thoughts, questions, or comments that would be > > > > appreciated. Here is the current proposal. > > > > > > > > https://etherpad.gnome.org/p/gsod-2021-proposal > > > > > > I'm trying to understand the scope and complexity of this. > > > > > > About how many pages are there to audit? > > > > > > > > > I don't know off hand. The first phase is to audit it to find the scope > > and then flag things for removal or flag for update. > > > Does this imply that both applicants and mentors do not know if the > proposal is about spending time reviewing a hundred pages or if the > proposal is about spending a bit more time reviewing a million pages? > > Yes, that's right - neither knows the scope. If I did the discovery then I would have by myself finished half of phase 1 already. But the exercise itself is valuable for the applicant and the mentor since I can also get an outsiders impression of what they've seen. > > > > > For the "work with community members", have those community members > > > committed to allocating sufficient resources? > > > > > > > > > I haven't secured any resources. In that particular case, when I say > > work with community members, I mean - asking the owner of that project > > - "is this information current or can I delete it" So the commitment is > > to answer questions about the utility of the content. Primarily I see > > my role here to make the introductions on how to talk to - eg I am the > > guide/map for stuff in the wiki. > > > Assuming it takes a while to identify the "owner of that project" > related to each page, and then finding ways to contact them (e.g. email > addresses), and assuming that 80% will not reply (that's more or less > my impression from trying to contact maintainers about their projects' > tickets left in Bugzilla a few months ago), how does this influence the > success criteria for this project and the motivation of the applicant? > So one of the things I had put in the proposal is for me to make executive decisions on particular pages if i have a high confidence that it is no longer active (eg no gitlab presence, no activity on existing bugs) I will make the decision to flag it for archive. One thing we are doing here is not requiring the candidate to make any decisions on the content other than to flag them (with help) - so it shouldn't create roadblocks where the candidate is busy waiting on someone. Once the content is flag I will announce on discourse and desktop-devel the archiving of the data. The updating of information is more tricky because if 80% do not respond then we'll need to figure that out but it should hinder the candidate's ability to continue the work. > > > > > > > > > > If it's about "building a better onboarding experience", is there an > > > analysis available what's bad about the current onboarding experience > > > with specific regard to the wiki? > > > > > > > > > Only the one analysis I did about two years ago when I went through > > them. > > There was enough wrong information that onboarding would have been > > confusing. I am not sure if I still have the etherpad where I had my > > notes there - but it was at our last combined hackfest with the docs > > team, engagement team and gtk team. That analysis/audit was only about > > 2 levels deep though. > > > Ah, great. Could you provide a link please? > Yeah, I don't remember the etherpad so unfortunately I don't have the notes. :/ It was about 2(?) years ago and probably already stale. But the outcome of that small bit of work is that I realized it was much more work
Re: Google Summer of Docs proposal 2021
Hi Andre! Great questions. I'll try to answer. On Mon, Mar 15, 2021 at 9:08 AM Andre Klapper wrote: > Hi, > > On Mon, 2021-03-15 at 08:11 -0700, Sriram Ramkrishna wrote: > > I'm working on a GSoD for this year and I've outlined the proposal. I > > just wanted to give you all a heads up. I'm mostly focusing on our wiki > > and looking to remove everything updated, and update the ones that are > > still valid. But we will also use that experience to build a better > > onboarding experience by building a more supportable project > > documentation setup that can be managed for the future. > > > > If you have any thoughts, questions, or comments that would be > > appreciated. Here is the current proposal. > > > > https://etherpad.gnome.org/p/gsod-2021-proposal > > I'm trying to understand the scope and complexity of this. > > About how many pages are there to audit? > I don't know off hand. The first phase is to audit it to find the scope and then flag things for removal or flag for update. > Does "remove" mean deleting pages (and making URLs become 404s if you > don't manually [[REDIRECT]]), or 'only' removing content from pages? > Remove means archive in this case. I don't want to delete anything permanently - they are historical and in the case of projects might be useful either to be possibly revived or for historical context. There are some that just have wrong information altogether and hasn't been touched in many years. Those will either be updated or retired completely. > For the "work with community members", have those community members > committed to allocating sufficient resources? > I haven't secured any resources. In that particular case, when I say work with community members, I mean - asking the owner of that project - "is this information current or can I delete it" So the commitment is to answer questions about the utility of the content. Primarily I see my role here to make the introductions on how to talk to - eg I am the guide/map for stuff in the wiki. > "looking at alternative documentation technologies" means potentially > replacing the MoinMoin installation by moving stuff to Gitlab (or so)? > Yes. But that's part of an overall revamp of our web infrastructure. It's due for a major rehaul and so the two need to work together. > If it's about "building a better onboarding experience", is there an > analysis available what's bad about the current onboarding experience > with specific regard to the wiki? > Only the one analysis I did about two years ago when I went through them. There was enough wrong information that onboarding would have been confusing. I am not sure if I still have the etherpad where I had my notes there - but it was at our last combined hackfest with the docs team, engagement team and gtk team. That analysis/audit was only about 2 levels deep though. Part of what I want to do is also start focusing on keeping metrics - so a better onboarding experience also means measuring things better within the project. > If it's about "building a more supportable project documentation > setup", is there an analysis about the current pain points and how this > plays along in combination with documentation in other places such as > help.gnome.org, GitLab wiki pages, or GitLab README.md files? > I'm not aware of any analysis - the idea of this project is to do exactly that. The idea is we build a proposal and that proposal has to include the current pain points (otherwise how does it become better?) and then we need to convince ourselves that this is a good solution going forward. I think the current wiki setup has not been particularly good if not altogether ignored. Part of that problem is our own set of process, but the bulk of our information is moving into gitlab and maybe gitlab is the right answer, but it needs to be investigated. I don't think this is an easy project to do - especially when it comes down to consensus. That's why the project is focused on a proposal as the end result - not to implement but at least debate. Cheers, sri > Cheers, > andre > -- > Andre Klapper | ak...@gmx.net > https://blogs.gnome.org/aklapper/ > > > ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Google Summer of Docs proposal 2021
Hey folks! I'm working on a GSoD for this year and I've outlined the proposal. I just wanted to give you all a heads up. I'm mostly focusing on our wiki and looking to remove everything updated, and update the ones that are still valid. But we will also use that experience to build a better onboarding experience by building a more supportable project documentation setup that can be managed for the future. If you have any thoughts, questions, or comments that would be appreciated. Here is the current proposal. https://etherpad.gnome.org/p/gsod-2021-proposal Thanks so much! sri ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Weekly docs standups
I've been doing active onboarding - setting up a meeting and talking about the project for extensions rebooted. I think that helps a lot, as I do get people showing up and they feel interested. On Fri, Oct 9, 2020 at 8:22 AM Shaun McCance wrote: > 100% yes. I should probably set up a wiki page about the standups to > manage expectations. I absolutely want them to be a place where new people > can drop in to get involved. > > On Thu, 2020-10-08 at 11:49 -0700, Sriram Ramkrishna wrote: > > I might advertise your meeting on GNOME africa telegram group. There are a > number of folks who are interested in documentation and this will give them > a chance to ask questions or ask some onboarding type questions. I hope > that is ok - just wanted to check with y'all first. > sri > > On Thu, Oct 8, 2020 at 8:51 AM Shaun McCance wrote: > > Hi all, > > I've brought up the idea of regular meetings in the past. I think the > best way to make them happen is to just do them. So, I'm going to start > doing a weekly standup every Tuesday at 11:00 US/Eastern. That's 15:00 > UTC right now, but I'm going to follow US DST. > > I chose this time because it is the most convenient time to get people > from the US west coast, US east coast, and Europe together during the > work day. I apologize to people who can't make it during the work day, > or who are in timezones where this is the middle of the night. We can > adjust accorind to needs, but this is the time I'm starting with. > > I think I successfully set up a room for us on meet.gnome.org: > > https://meet.gnome.org/b/sha-muk-akl-apm > > I hope to see you Tuesday, October 13, at 15:00 UTC. > > Thanks, > Shaun > > > ___ > gnome-doc-list mailing list > gnome-doc-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-doc-list > > ___ > > gnome-doc-list mailing list > > gnome-doc-list@gnome.org > > > https://mail.gnome.org/mailman/listinfo/gnome-doc-list > > > ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Weekly docs standups
I might advertise your meeting on GNOME africa telegram group. There are a number of folks who are interested in documentation and this will give them a chance to ask questions or ask some onboarding type questions. I hope that is ok - just wanted to check with y'all first. sri On Thu, Oct 8, 2020 at 8:51 AM Shaun McCance wrote: > Hi all, > > I've brought up the idea of regular meetings in the past. I think the > best way to make them happen is to just do them. So, I'm going to start > doing a weekly standup every Tuesday at 11:00 US/Eastern. That's 15:00 > UTC right now, but I'm going to follow US DST. > > I chose this time because it is the most convenient time to get people > from the US west coast, US east coast, and Europe together during the > work day. I apologize to people who can't make it during the work day, > or who are in timezones where this is the middle of the night. We can > adjust accorind to needs, but this is the time I'm starting with. > > I think I successfully set up a room for us on meet.gnome.org: > > https://meet.gnome.org/b/sha-muk-akl-apm > > I hope to see you Tuesday, October 13, at 15:00 UTC. > > Thanks, > Shaun > > > ___ > gnome-doc-list mailing list > gnome-doc-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-doc-list > ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Let's start talking
I would love to help arrange a virtual hackfest. Let me know what you think about that.. we were supposed to do "west coast hackfest" again but because of the current issues we can't. Maybe we can experiment? I'm also interested in having the docs team be a partner in the scalable onboarding process that I'm working on. We can even talk about that some. Here is the initiative - https://gitlab.gnome.org/Teams/Engagement/initiatives/scalable-onboarding It kind of works into some other incubation projects I am working on in regards to metrics. I would love to work with all of you on how to implement onboarding so that we can help grow the team and make documentation that has a lot of people working on it. sri On Fri, May 15, 2020 at 1:46 PM Michael Hill via gnome-doc-list wrote: > > On Fri, May 15, 2020 at 2:02 PM Petr Kovar wrote: > > > I'm. I like the idea but finding the correct time is always difficult. > > Maybe just pinging folks on IRC to see who's online to chat would work > > better for a start? > > Most afternoon times CET would work for me. > > Mike > ___ > gnome-doc-list mailing list > gnome-doc-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-doc-list ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Documentation Portal Meeting Minutes - 2018-04-18
Link to the minutes on Gitlab - https://gitlab.gnome.org/Community/DeveloperPortal/wikis/Meetings/2018-04-18 Meeting Minutes as follows: Attendees: * Ken * Sri * Michael Agenda: * developer portal server status - https://bugzilla.gnome.org/show_bug.cgi?id=794984 Not complete, put a note for an update - * Outcome of the conversation on DDL - https://mail.gnome.org/archives/desktop-devel-list/2018-April/msg8.html Good to know all the other efforts that were out there, especially the mockups by Allan Day which addresses - : https://gitlab.gnome.org/Community/DeveloperPortal/issues/9 * default language - There are two issues here, the long term issue of getting language communities to incorporate gobject as part the language paradigm. This is difficult as we will need someone who understands GObject to go into the various language communitues and argue for incorporating GObject as part of the language as part of an overall "GUI support'. Some languages for instances, implicitly support a basic GUI, we could make that GObject/GTK+. This comes from the DDL thread and specifically by ebassi. The other issue is that we need something for the short term, and that means we need to create a guide that has a preferred language for a new developer, but doesn't try to exclude other languges. This is so that we have a basis for people to start from. What language we pick is ased on the following criteria: * reasonable toolchain (integration with GNOME Builder) * good API docs (we should be able to create documentation on the portal and it gets shown in Builder) Would be nice to have identical content in Builder and documentation portal * Documentation that is manageable, searchable, complete, and up to date We need an on-going dicsussion on what that language should be. (Michael will lead that with Phllip, Sri will talk with Christian) Actions: * Michael to build Django templates from Allan's mockup site: TODO * Sri to follow up on hosting on GNOME infrastructure: TODO * Ken to work on database backups of the dev site: TODO * Michael to talk to Philip Chimento about JS API docs & toolchain: TODO * Sri to talk to Christian about Builder support & integration: TODO * Sri to get representation from GNOME docs team, and perhaps decide a new meeting time if it makes sense: TODO ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: late coming features
On Thu, Mar 5, 2015 at 10:54 AM, Matthias Clasen wrote: > On Sun, Feb 22, 2015 at 11:54 AM, Jim Campbell wrote: > >> I've created a branch for the notification-related updates. Please do >> this work on the wip/3-16-notification-update branch. Once we get the >> notification-related docs into good shape, we can merge them to master. >> > > Hey Jim, thought I should follow up - did you get any updates for > notification changes into the docs ? Still need help ? I have sucked at helping promote this 3.15.91 release. Still want me to push an image out there for people to test out? sri > ___ > release-t...@gnome.org > https://mail.gnome.org/mailman/listinfo/release-team > Release-team lurker? Do NOT participate in discussions. ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: GNOME Documentation Promo Video Feedback (Rev 2)
On Wed, Jul 16, 2014 at 12:30 PM, Bastian Hougaard wrote: > Thanks for the feedback, everyone! > > I have addressed most feedback [1], and come up with a final revision. If > there is any last thoughts, feel free to vent them (with timestamps) here: > > https://wiki.gnome.org/BastianIls%C3%B8/DocumentationVideo/draft3 > > I'll try to coordinate the release of the video with Engagement at the next > meeting or so. Ideas for that are also welcome in this thread. > Pretty good, I'm quite pleased with the result. There is one thing though, one of the parts has a darkened area on the bottom right. Do you know why? sri > -Bastian > > [1] = Adressed feedback are the stroked items at > https://wiki.gnome.org/BastianIls%C3%B8/DocumentationVideo/draft2 > If Karen is up to it, unstroked voice-over items will be addressed before > release. :) > > ___ > engagement-list mailing list > engagement-l...@gnome.org > https://mail.gnome.org/mailman/listinfo/engagement-list > ___ gnome-doc-list mailing list gnome-doc-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: GNOME Sound
On Tue, Dec 7, 2010 at 3:03 PM, Paul Cutler wrote: > I'd recommend Joey (cc'd) - he's active in GNOME marketing and has a > musical background. > > Gosh, you know I would really love a nice asian sound or myabe a voice from carnatic or hindustani music. It's kind of hard to describe what I have in my head but it's traditional but somewhat choral in nature. I'm not sure if using voices will pan out but it's hard to find subtle sounds for these kind of things. Anyways, just a thought. sri ___ gnome-doc-list mailing list gnome-doc-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: 2.18 release notes
You should ask the GNOME Journal folks as well. They might be willing to do something as well. sri On Mon, 2007-02-12 at 12:42 -0800, Ryan Paul wrote: > Quim Gil is looking for some help with the 2.18 release notes. I noticed > his blog entry on planet.gnome.org and figured that it would be a good > idea to relay the message here. I helped out a little bit with the 2.16 > release notes and I'll probably do the same again this time. Anybody > else who is interested in helping, check out the following web sites: > > Quim's blog entry is here: > http://desdeamericaconamor.org/blog/node/333 > > The current outline for the release notes is here: > http://live.gnome.org/TwoPointSeventeen/ReleaseNotes > > -- Sriram Ramkrishna <[EMAIL PROTECTED]> ___ gnome-doc-list mailing list gnome-doc-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Hello!
Welcome aboard. :) sri On Thu, Mar 23, 2006 at 07:09:08PM +, Alvin Sipraga wrote: > Hello. I'm Alvin (Sipraga) and I'd like to join the GDP. > I really enjoy writing documentation for applications, so I hope I can > be of use in that department :). > I'm not sure what else to say, so there it is. > ___ > gnome-doc-list mailing list > gnome-doc-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-doc-list -- ___ gnome-doc-list mailing list gnome-doc-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Introduction of Alexander Shopov
Welcome, Al! :) sri On Fri, Oct 21, 2005 at 11:42:03AM +0300, Alexander Shopov wrote: > Hi everybody, > > My name is Alexander Shopov and I am the leader of the Bulgarian Gnome > translation team. We have already finished the translation of the core > interface and we are gradually starting to look at the documentation. > In the following months I expect us to finish the tranlastion of the > documentation of several modules and converting the ready translations > to the Gnome docbook format. > I have subscribed to gnome-doc-list to be in touch with the > documentation changes and I have subscribed to gnome-doc-devel-list to > look at the changes in the tools. > I hope to be able to make some commits during next week but I cannot > promise that. > I have still not read everything on Gnome site about documentation > translations and if there are resources I need to take in mind i'll be > thankful if you lead me to them. > > Best regards: > al_shopov > > ___ > gnome-doc-list mailing list > gnome-doc-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-doc-list -- ___ gnome-doc-list mailing list gnome-doc-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Sun documentation team.
Probably talk to teh Sun Doc team, but also to Shaunm McCance who owns the GNOME documentation project.. sri On Tue, May 24, 2005 at 11:10:59PM -0600, Mario Carrión wrote: > On 5/24/05, Rajeev Jain <[EMAIL PROTECTED]> wrote: > > Hi Pat > > > > How about passing the work to volunteers? > > I would like to help :) > > Regards > > Mario Carrión <[EMAIL PROTECTED]> > > > > Rgds > > > > Rajeev Jain > > http://api-writing.blogspot.com/ > > > > - Original Message - > > From: "Patrick Costello" <[EMAIL PROTECTED]> > > To: > > Cc: "Bill Haneman" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Peter > > Korn" <[EMAIL PROTECTED]> > > Sent: Tuesday, May 24, 2005 10:52 PM > > Subject: Sun documentation team. > > > > > > > Hi, > > > > > > Due to pressure on documentation team resources, Sun can no longer > > continue > > > to update or maintain the following items: > > > > > > - gcalctool Help manual > > > - GOK Help manual > > > - Gnopernicus Help manual > > > - GNOME Accessibility Guide > > > - GNOME Documentation Style Guide > > > > > > We will be putting our current updates into CVS in the next week or so. > > > > > > Pat Costello, > > > Sun JDS Documentation Team. > > > > > > ___ > > > gnome-doc-list mailing list > > > gnome-doc-list@gnome.org > > > http://mail.gnome.org/mailman/listinfo/gnome-doc-list > > > > ___ > > gnome-doc-list mailing list > > gnome-doc-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/gnome-doc-list > > > ___ > gnome-doc-list mailing list > gnome-doc-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-doc-list -- ___ gnome-doc-list mailing list gnome-doc-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-doc-list
Re: Sun documentation team.
On Tue, May 24, 2005 at 06:22:28PM +0100, Patrick Costello wrote: > Hi, > > Due to pressure on documentation team resources, Sun can no longer continue > to update or maintain the following items: > - Gnopernicus Help manual > - GNOME Accessibility Guide This is sad considering Sun is one of the big proponents of GNOME Accessibility. It's unfortunate that we lose documentation people where we are at our weakest and continuing to be our weakest part of our DE. :/ I'm wondering if just the nature of how we do documentation is somewhat at fault here. We need to try something new I think. sri ___ gnome-doc-list mailing list gnome-doc-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-doc-list
