We have contacted a number of groups individually, but due to a number of reasons it has been difficult to find an appropriate contact person. This is especially true for Python User's Groups with websites not presented in English.
If you are from a country where English is not the primary language, we would be happy to present the article in the original language alongside an English translation.
If you would like to participate, but are unsure about what to
include, here are some suggestions:
* Where the user group is based
* Who are the active members
* How long the group has existed for
* How frequently meetings are held
* Any particular programming interests held by members
* Upcoming events
* Photographs of the local area
* Information on local culture
* Comments on how Python is used in your country
Please email firstname.lastname@example.org for more information, where a member of the editorial board will be able to respond promptly to your query.
Submissions may be academic or industrial. Academic submissions will undergo a peer-review process prior to final publication, while industrial submissions may be reviewed by the editorial board.
In order to allow sufficient time to complete the review process, we must start collating entries now. Academic and Industrial proposals will be accepted until and including January 8th. Following this will be a review period, with final submissions due February 9.
We are happy to include submissions on a wide array of topics, including but not restricted to:
* Research articles
* Web technologies -- frameworks, implementations, discussions, proposals etc
* Request for comments -- code submissions for discussion and review by The Python Papers team
* Events listings -- please let us know of any local events happening during the next quarter in your area
* Python User Group focus articles. It would be great to have content from all around the globe to highlight the breadth of takeup of Python and bring people closer together.
Please email any submissions or queries to email@example.com where one of the editorial board members will be able to promptly respond.
Some of the highlights have included being contacted individually by readers who share an interest in particular topics or have something to say. It is this kind of response that will eventually give the journal a life of its own beyond what is injected by the editorial board. Moving towards this state is highly desirable.
I would love to see, for example, connections being made through the articles in the magazine. On this basis, I would like to encourage people to email comments for publication to firstname.lastname@example.org of about 20-70 words, letting us know of their specific interests. Please include a statement about what form of attribution you would like us to include, otherwise we will post letters anonymously.
The journal is released under the Creative Commons License, subject to Noncommercial, Attribution and Share-Alike conditions. Emailing to email@example.com indicates the author's agreement to releasing their comments under this restriction. It is also for this reason that we cannot include comments from newsgroups or personal emails without explicit permission of the authors.
The first edition is out, and is percolating through the Internet as we speak. God speed, little journal!
While a great deal of the editorial focus is now on the next version, let's do a little bit of navel-gazing on what we have achieved so far.
* Journal registration. We now have our very own ISSN number. There are many like it, but this one is ours. It is a small badge of respectability which will allow us to start to build a good reputation, and step up to fill some of the information gaps in the Python community.
* Academic articles. We've published one, and another has been submitted. While the most popular (read elite) journals may always have their 'pick' of articles, we have two things going for us: (1) We promote freedom of information -- this means something to some people; (2) We are more focused, and as such may become a better source for Python than other generalist journals.
* Industry articles. We've published one, and have more on the way. In the case of the Python Papers, these articles are not merely extended advertisements as in the case of many more glossy productions, but in-the-trenches works covering real problems and solutions.
* Diversity. While in a sense we are very Australian at this stage, the editorial board are not just 'a bunch of mates', although we are becoming fast friends as we all work together. We represent a diversity of backgrounds and opinions, something which I feel brings vitality and energy.
* A move away from the 'heroic' model of article production. Expert blogs are a wonderful source of information, but this puts enormous load on individuals to keep producing great articles, and is also isolationist. By moving away from any particular individual, the Python Papers can bring in any voice without being tribal.
We hope this recommends us to you.
Welcome to The Python Papers. This journal, small though it is, represents the careful efforts of a small group of Python enthusiasts who are keen to form a better community in which developers may work.
As Editor-In-Chief, my role is manifold, but my goals are to improve the level of connectedness of Python developers, and in so doing improve my own developer experience.
The entire editorial board has put time into making this publication something which will hopefully lead to a buildup of momentum, fuelled by the enthusiastic involvement of others who find Python as exciting as we do.
The current issue contains one academic, peer-reviewed article, one industry article, and a list of events coming up in Melbourne, Australia. We would like to expand this list significantly. We offer our services in organising, collating and reviewing submitted content such that Python developers around the world may participate in the creation of something bigger than all of us, for the benefit of all of us. It may be a small journal, a little thing really, but all are welcome, and we look forward to getting to know our readers through the written word.
Please download the first edition, and consider both what it is and what it might be.
For those of you looking to publish an academic paper as a part of coursework or for interest's sake alone, we can offer a formal review process which will meet those guidelines while preserving the goals of freedom of information and community spirit.
Those who are using Python in their work may like to consider using the journal as a means of expressing successes or frustrations with either the language itself or specific applications. We may be able to offer code reviews and style guides, and would be happy to hear about and help propagate news of what is happening so that everyone can take an interest.
For those who would like a reliable source of information, The Python Papers presents a unique and current view into the state of Python at large.
To all of you, welcome!