> > > > > > *The API docs are actually not too hard to work on - in a lot of placesthe > docs have already been sketched in but need technical writing > forcopyediting and clarification. If you're interested in working in > thisarea (esp. if you want to focus on legacy docs), I can give advice.*
> > > > > *One hitch that should be mentioned (if Xavi hasn't already) is that EFLis > currently in the midst of a transition that is going to introduce anew set > of APIs. Unfortunately this work is unfinished, and this canmake writing > tutorials more challenging than you might expect (althoughno less > necessary).* In that case, I'd be happy to start my work on the API docs. If I have any questions, I'll know where to direct them. As for EFL, I'm up for a challenge. How can I begin working on the API docs? Should we start a one-on-one correspondence, Bryce? I don't want to be nuisance, but I could use some assistance getting up and running. *As you can see, Mike is our Minister of Redundancy Minister.* Nice to meet you, again, Minister of Redundancy Minister Mike. : ) Best, Matt On Wed, Aug 8, 2018 at 3:47 PM, Bryce Harrington <br...@bryceharrington.org> wrote: > On Wed, Aug 08, 2018 at 03:13:29PM -0700, Matthew Zamudio wrote: > > Hi Bryce, > > > > For now, I'm most interested in working with: > > > > - API documentation > > - Tutorials > > - End-user documentation > > > > Based on the name at least, high level projects should probably wait > until > > I complete some lower level tasks. > > > > I will most likely require some guidance with API, but I can teach > myself a > > lot once I have a definite task and direction. As for tutorials and > > end-user documentation, I should be able to handle those on my own. > > The API docs are actually not too hard to work on - in a lot of places > the docs have already been sketched in but need technical writing for > copyediting and clarification. If you're interested in working in this > area (esp. if you want to focus on legacy docs), I can give advice. > > One hitch that should be mentioned (if Xavi hasn't already) is that EFL > is currently in the midst of a transition that is going to introduce a > new set of APIs. Unfortunately this work is unfinished, and this can > make writing tutorials more challenging than you might expect (although > no less necessary). > > Bryce > > > Best, > > Matt > > > > On Wed, Aug 8, 2018 at 3:03 PM, Bryce Harrington < > br...@bryceharrington.org> > > wrote: > > > > > On Wed, Aug 08, 2018 at 10:38:53AM -0700, Matthew Zamudio wrote: > > > > Hi all! > > > > > > > > My name is Matt Zamudio and I'm very new here. I hope to help out at > > > > Enlightenment with documentation. Currently, I work as a writer and > > > editor > > > > at an online publishing website in the San Francisco Bay Area. I'm > > > looking > > > > to transition from the journalism and editorial fields to technical > > > > writing, and figure this is a good place to start. > > > > > > > > Please let me know if there is anything I can immediately get > started on. > > > > Otherwise, I'll continue my correspondence with Xavi and go from > there. > > > > > > > > Looking forward to working with all of you. > > > > > > > > Best, > > > > Matt Zamudio > > > > > > Hi Matt, > > > > > > There are four general categories of documentation work Enlightenment > > > and EFL need presently, at least, that I've seen: API documentation, > > > tutorials, high level project/architectural, and end user > documentation. > > > > > > Each of these categories is broad with many subcategories of work items > > > within them. Some areas have gotten more attention than others, some > > > have more urgent need of attention, some require deeper experience with > > > the project than others. Some areas have people who can give guidance, > > > others you'd be more on your own to figure out what's needed. > > > > > > What are your personal druthers regarding the above? It'd help in > > > getting you pointed in the direction you want to go. > > > > > > Bryce > > > > > > ------------------------------------------------------------ > > > ------------------ > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > > > enlightenment-devel mailing list > > > enlightenment-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
