Hello Aymeric -- Yes indeed, I misunderstood. Thank you for lining things out for me. Loosely, the group I am talking about is the group of a couple thousand who completed that survey in the first 48 hours. It would be great to know why a lot of those ~2000 folks feel so stongly and positive about the documentation. I don't know how to organize this. With all due respect, I was hoping the mechanism you outlined could kick-in to facillitate this.
As for other thread in my proposal <https://en.wikipedia.org/wiki/User_analysis>, the way I would approach this would be on a foundation of the mass media research of Phillip Palmgreen with 'uses and gratification' theory which is rooted deeply in Fishbein's 'expectancy-value' theory with perhaps some Charles Osgood thrown in for good measure. All this stuff is from the eighty's -- possibly somewhat out-of-date. So, you are a mathematician, huh? How are your statistics? And this might be some kind of non sequitur, but in any case, I looked at the text files from GitHub that comprise our published documentation. I am attaching two files. One is a list of words used 50 or more times. I don't know how words like 'youll' made it in there, but a lot of these words are good candidates for the Glossary. Also, enclosed is another file listing the file sources for these words. Thanks again, On Saturday, January 2, 2016 at 4:51:15 AM UTC-5, Aymeric Augustin wrote: > > On 2 janv. 2016, at 05:48, Doug Epling <wmdoug...@gmail.com <javascript:>> > wrote: > > > First is, has been, a discussion open for spectators but limited > participants to core members. Asside from its subject pertaining current > state and future path, all other details are above my pay grade. > > Hi Doug, > > I’m afraid there’s a misunderstanding of how this community operates. > > "Team members” — we de-emphazised the “core dev” terminology in 2014 > because it over-valued writing code — are people who have made consistent, > constructive contributions to Django, usually starting small and then > moving on to more ambitious projects. Albeit slow, this process is the best > way we have found for new contributors to gain trust from existing > contributors. > > There needs to be some mechanism to give a consistent direction to the > Django project. Currently we have two layers of decision: community > consensus and technical board arbitration vote. Obviously voices of team > members matter more in community discussions. We hope that’s because of > their experience with Django and the quality of what they say, not just > because they carry a “team member” flag. Arbitration votes almost never > happen. (There was only one, ever, to drop support for IE8 from the admin.) > > In practice, team members tend to have busy professional lives outside of > Django. This has stalled many projects in the past. For this reason we > structured our organization in order to empower community members as much > as possible and to require as little input from the Django team as > possible. > > We wouldn’t find a core-only conversation nearly as useful as a > community-wide discussion. Perhaps that’s why core panels have fallen out > of fashion at DjangoCons during the last couple of years. And we definitely > don’t want contributors to censor themselves because of perceived pay > grade. > > The only pre-requisite to tackling massive projects such as “let’s > restructure the whole documentation” is to have built enough trust from the > current team for everyone to know that you will complete it in good > conditions. Building that trust requires completing successfully small > projects, then increasingly large ones. Team membership may be offered at > some point in that process. > > I hope this helps, > > -- > Aymeric. > > -- 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/00f54342-b056-4b8d-8165-c921777cc11d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
404 ability able abstract accept accepted accepts access according account action actions actually add added adding addition additional address adds admin aggregate algorithm alias allow allowed allows already also always another anything apache api app appear application applications applied apply appropriate apps arent args argument arguments around article associated attribute attributes authentication author authors automatically availability available avoid aware back backend backends bar base based basic becomes behavior best better block blog book books boolean box branch browser bug builtin cache cached caches caching call callable called calling calls can cant care case cases cause certain change changed changes character characters check checks child choice choices class classbased classes clause clean client code column comes command commands comment commit common compatibility complete complex configuration configure configured connection consider considered contain containing contains content contents contenttype context control convenience convert converted cookie cookies coordinate coordinates copy core correct correctly corresponding count create created creates creating csrf current currently custom customize data database databases date datetime day decorator def default defaults define defined defines delete dependencies depending deprecated described description detail details determine developers development dictionary difference different directly directory display displayed distance django djangoadmin djangoconfurls djangodb djangohttp djangos docs document documentation doesnt domain done dont easily easy edit effect either element else email empty enable enabled encoding end engine engines ensure entire entries entry environment equivalent error errors etc even every exact exactly example examples except exception exceptions execute executed exist existing exists expected explicitly expression expressions extra false feature features feed feeds field fields file filename files filter filters finally find first fixture flag follow following follows foo foreign form format formats forms formset found framework full function functionality functions future general generally generate generated generic geodjango geographic geom geometries geometry get gets git give given good group handle handler handlers handling happens header headers headline hello help heres host however html http https idea implement implementation import important include included includes including index individual information inheritance initial input inside install installation installed installing instance instances instead integer interface invalid isnt issue issues item items javascript json just keep key keys keyword know kwargs label language last later latest layer least length less lets level library like limit line link list listed lives load loaded loader loading local locale location log logging logic login long longer look looks lookup lookups made make makes making management managepy manager managers manually many manytomany match matches matching maximum may means media memory message messages meta method methods middleware might migration migrations mode model models modified modify module modules month much multiple must mysql myviewrequest name named names namespace necessary need needed needs never new next none normal normally note notes now null number obj object objects often old one open operation operations option optional options oracle order ordering original otherwise output override package page pages parameter parameters parent part particular pass passed passing password patch patches path paths pattern patterns people perform performance performed permission permissions person pip place please point points polls port possible post postgis postgresql prefix present prevent previous primary probably problem problems process processing production project projects property protection provide provided provides providing proxy pubdate public published publisher pull put python pythons queries query queryset querysets question raise raised raises range raster rather raw read reason recommended redirect refer reference register regular related relation relationship relationships release releases remove removed render rendered rendering representation represented representing represents request requests require required requires response result resulting results retrieve return returned returns reverse right root rows run running runs safe save saved say second seconds section security see select send sent separate serialized server servers session sessions set sets setting settinginstalledapps settings setup several signal signals similar simple simply since single site sitemap sites small something sometimes source spatial spatialite special specific specified specify specifying sql sqlite srid standard start state static status steps still storage store stored stores str string strings subclass subclasses subject suite support supported supports sure synopsis syntax system systems table tables tag tags take takes team tell template templatename templates test testing tests text thats theres theyre things though three thus ticket tickets time times timezone title together token top transaction translation translations true try tuple tutorial two type types typically unicode unique unless update upload uploaded url urlconf urlpatterns urls usage use used useful user username users uses using usually utf8 valid validation validationerror validators value values variable variables version versions via view views want way ways web well whether whose widget widgets will within without wont words work working works world write writing written year youd youll youre youve zone
base.txt, signing.txt, database-functions.txt, generic-editing.txt, admindocs.txt, sql.txt, modwsgi.txt, email.txt, admin.txt, api.txt, flatpages.txt, index.txt, distributions.txt, middleware.txt, mixins-single-object.txt, commands.txt, forms-api.txt, conditional-expressions.txt, coding-style.txt, organization.txt, relations.txt, deployment.txt, custom-management-commands.txt, design-philosophies.txt, howto-release-django.txt, widgets.txt, mixins2.txt, actions.txt, api-stability.txt, utils2.txt, custom-file-storage.txt, tutorial01.txt, install2.txt, submitting-patches.txt, lookups2.txt, install.txt, outputting-csv.txt, index2.txt, default.txt, staticfiles.txt, unit-tests.txt, validators.txt, sitemaps.txt, .Rhistory, logging.txt, storage.txt, legacy-databases.txt, signals.txt, upgrade-version.txt, contents.txt, generic-editing2.txt, modelforms.txt, checklist.txt, templates.txt, sitemaps2.txt, measure.txt, localizing.txt, jython.txt, translation.txt, tablespaces.txt, security2.txt, meta.txt, formsets2.txt, security.txt, deployment2.txt, managers.txt, mixins-multiple-object.txt, initial-data.txt, javascript2.txt, error-reporting.txt, transactions.txt, feeds.txt, migrations.txt, instances.txt, contenttypes.txt, mailing-lists.txt, new-contributors.txt, glossary.txt, conditional-view-processing.txt, overview.txt, django-admin.txt, geoip.txt, mixins-editing.txt, urls.txt, humanize.txt, external-packages.txt, lookups.txt, writing-migrations.txt, tutorial03.txt, tutorial.txt, install3.txt, checks.txt, multi-db.txt, reusable-apps.txt, options.txt, many_to_many.txt, contributing2.txt, geos.txt, deprecation.txt, one_to_one.txt, customizing.txt, serializers.txt, geoquerysets.txt, shortcuts.txt, urls2.txt, messages.txt, redirects.txt, file-uploads.txt, tutorial04.txt, db-api.txt, unicode.txt, aggregates.txt, media.txt, migration-operations.txt, testing.txt, writing-documentation.txt, aggregation.txt, operations.txt, cache.txt, optimization.txt, schema-editor.txt, language.txt, functions.txt, validators2.txt, models3.txt, admin2.txt, geoip2.txt, tutorial06.txt, applications.txt, file.txt, checks2.txt, generic-views.txt, fields2.txt, auth.txt, functions2.txt, sites.txt, request-response.txt, mixins.txt, models.txt, windows.txt, mixins-date-based.txt, generic-display2.txt, gunicorn.txt, roles.txt, sessions.txt, whatsnext.txt, csrf.txt, class.txt, fields3.txt, many_to_one.txt, layermapping.txt, settings2.txt, fields.txt, javascript.txt, decorators.txt, working-with-git.txt, databases.txt, middleware2.txt, help.txt, overview2.txt, committing-code.txt, uwsgi.txt, exceptions.txt, serialization.txt, upgrading.txt, tutorial05.txt, builtins.txt, flattened-index.txt, over50, git.txt, formsets.txt, python3.txt, generic-date-based.txt, expressions.txt, release-process.txt, timezones.txt, mixins-simple.txt, formatting.txt, models2.txt, troubleshooting.txt, files.txt, bugs-and-features.txt, api2.txt, uploads.txt, forms.txt, utils.txt, performance.txt, triaging-tickets.txt, team.txt, tools.txt, custom-template-tags.txt, settings.txt, validation.txt, signals2.txt, apache-auth.txt, tutorial02.txt, model-api.txt, auth-remote-user.txt, custom-lookups.txt, custom-model-fields.txt, urlresolvers.txt, gdal.txt, usage.txt, views2.txt, advanced.txt, intro.txt, tutorial07.txt, passwords.txt, outputting-pdf.txt, ogrinspect.txt, querysets.txt, template-response.txt, syndication.txt, generic-display.txt, views.txt, contributing.txt, queries.txt, pagination.txt, clickjacking.txt, general.txt,
