For the third and final time, I appologize.
On Tuesday, January 5, 2016 at 11:50:51 AM UTC-5, Doug Epling wrote: > > This thread is aimed at the specific issue pertaining to the Django > Glossary. > > But first, after noticing, by accident, a huge spike of views on my G+ > profile I think I should explain. I don't use G+ much because it seems > kind-of goofey to me -- that's just me. If you want to see the real > picture, you can look me up on LinkedIn.com under Douglas Epling. > > As a web-services/python-programmer-analyst I will never hold a candle to > any of the lot of you in this community. A while back I tried to make a > career change by paying my dues in blood, sweat, and tears (not to mention > $) by earning a BS in Computer Science as a middle-aged geek wannabe. This > personal initiative was thwarted by the 'tsunami', as Christine Lagarde > called it, of 2008. > > I am proud that during those academics and unitl this day, I am a Linux > afficianado. I use a Fedora desktop daily, exclusively. Richard Stallman > is my hero. And just as I was uncerimoniously being kicked out the door of > this enterprise where I'd been testing security features on embedded > software of network printers, I discovered Python. > > Although not a software developer, I know quality in technology when I see > it. Hint: Microsoft ain't it. The millenium edition was my first clue! > So, I am drawn to the Django community for the promise of caskets filled > with gold coins, rubies, and emeralds ... just kidding; I'm a kidder. > > So, the glossary! Yep, it's still there. I could swear I saw an > invitation in the form of a hyper-link to work on the glossary, although I > can't seem to locate that in the documentation at this point. In fact, it > almost appears the glossary is being slowly shunted into obscurity. > > Here's the thing: I have taken the liberty of parsing the text documents > comprising the Django documentation. > <https://groups.google.com/d/msg/django-developers/QW06ctKbFKA/Tnkx0Io_EQAJ> > I have identified a lengthy list of candidate terminology for possible > inclusion in the glossary. But problems like this simply can not be solved > with the same methods used to develop code. Can you imagine 600 pull > requests to add or modify single terms and their meanings? > > If this is too hard, I'm hep! But what if we established a moin, open to > anyone who wants to register, where the glossary can be developed? And > establish some kind of temporal cycle with pull requests for glossary > updates. > > Yours truly, > > PS > > A Django v2.0 goal for revised and enhanced documentation was unrealistic, > and is hereby revoked. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ced6a83f-6b2b-4357-bafc-e5b65c72e497%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
