My coding work lately has focused on a major upgrade to Planeteria by giving it a web framework (currently it has none). The framework I chose was Flask, because of its simplicity, its flexibility, and its scalability. It has a strong community and documentation, which makes our project more friendly to new contributors, and has several add-ons for features that we hope to implement/improve upon for the site down the road, which will make future improvements to the site much easier. I’ve also done some reorganizing of the files so that there’s clearer separation of the business logic and presentation logic. Again, this should make the site more friendly to new contributors who might want to edit the backend Python code without unintentionally altering the page content. The page layout is in Bootstrap, which is another tool that is commonly used and well documented. It’s often used by developers for prototyping, with some handy defaults for buttons, blocks of text, etc. Although you may notice that many projects and websites that have a very similar look because of this, it provides a foundation that is very easy to alter through CSS that a skilled designer could do a lot more with.
This week I created a schema for the data in SQLite3 and did a crash-course in SQLAlchemy to work with that data. Currently, Planeteria stores its data in sqlite with the help of a tiny tool that simply stashes it as if it’s a dictionary; there is no schema. This has been a huge frustration of mine, as it’s difficult to see exactly what data is stored in what format. Not ideal when trying to debug Unicode issues and character escaping.
I now have planet data (name/description/slug) and a planet’s feed data (feed name/url/image/planet id) saving to a database, with the ability for a planet admin to update any of that data correctly. With just a few sql commands, I can now check the database and see if my code did what it should with the data. Huzzah! This led to a few revisions of the schema, each time simply deleting the database and creating a new one with the updated schema, then more testing. Last night, I did some rigorous testing, trying my hardest to “break” it (identify flaws). The biggest test was using unicode characters and quotes; two things that cause problems right now if they’re entered in the admin page. It saved and loaded the data exactly as it should! It’s lovely when things just work as they’re supposed to.
The database does not yet save feed content data. It’s still to be determined exactly how that will be saved. I’ve talked before about adding tagging to the site to help people more easily identify content within a planet that is relevant to them. Since the only users on the site are the planet admins, the planet admin would be responsible for assigning tags to each feed; but how would the admin correctly guess what tags would most interest the planet readers? I think it just puts an undue burden on the planet admin for maintaining all the tags for their planet feed. Additionally, admins can edit a blog’s feed data but they have no control over individual blog entries; the topics discussed by a blogger in the planet might vary greatly, making an individual tag that brings up that blogger’s entries only applicable to some, not all of those entries.
I’m not sure that adding individual user logins for readers to save personally selected tags is the right solution. It seems overly complicated and potentially underused. I’d want to wait to see if there is really demand for this; as it is, many readers are simply reading the feed in their own feed readers anyway. A much simpler solution that would enable readers to find content most relevant to their interests is a Search window.
I bring all of this up because how the feed content data is used/accessed will guide the decision of how it’s saved. A relational database would be an appropriate way to store feed tags, but if we want users to be able to search the content, storing it in a server designed for searching such as Solr or Elasticsearch might be more appropriate.
While I mull that over, there are plenty of other things to do with the Admin page functionality I’ve built so far: next on my plate is form validation, security, and error reporting. Then, adding user logins, most likely with Mozilla Persona.
I just completed my registration for Pycon, a big conference for pythonistas which will be held in Santa Clara, CA this March. I’m so thankful for the financial aid that made it possible for me. I’m looking forward to getting to know more Python coders; almost everyone I have met so far in the Portland Python community is really cool and welcoming and I’m hoping that it extends to the larger population of Pythonistas who will be at Pycon.
This is will be my first Pycon, and someone pointed me to this very helpful beginner’s guide which gives some general conference-going tips (don’t forget to eat and shower. seriously.) as well as suggestions for beginner-friendly sessions at the conference.
I’ve signed up for a few tutorials; I’m a bit bummed to miss the session about scraping and public data hacking, but it conflicts with one that’s more directly related to my work on Planeteria, Rapid Web Prototyping with Lightweight Tools. It’ll cover two lightweight tools that I’m using for this project (Flask and Twitter Bootstrap) so I’m sure I’ll pick up some handy tips. I’m also looking forward to rounding out my web dev knowledge with a database crash course.
As I’ve been active in the Portland Pyladies chapter, I’m looking forward to meeting Pyladies from other parts of the country at the Pyladies lunch on Saturday. I also plan to check out the Ada Foundation’s feminist hacker lounge, which I actually learned about through the WFS Planet feed.
Finally, some folks in the PDX Python user group have convinced me to stay for the sprints.
There’s discussion of a meetup with bay area OPW interns as well; if anyone is interested who I have not yet spoken to about this, let me know.
This week is the first week of my GNOME OPW internship. I’m honored to have been selected as a participant and I’m especially excited to dive into my project. This will be my first formal contribution to an open source project, hopefully the first of many.
My internship project is to make improvements to Planeteria.org, a blog aggregator. Those involved in the internship should be familiar with this site since the interns are required to blog and our blogs are added to the Women in Free Software planet.
My degree and professional experience is in online communication, so I’m approaching this project from a communication/media perspective. My existing tech skills are in website design & development; while I still have a lot to learn, I know enough to dive in without a steep learning curve. My three major goals for the project are to:
- Improve the user experience for Planet users and enable subscribers to build community.
- Help people better understand the value and potential of the blog aggregator tool; how other people use it, how they might use it.
- Generate support for the project (donors, contributors, users).
I’m starting with a redesign that will modernize the code and make the site more aesthetically appealing for visitors. I’ll be using Twitter Bootstrap, which has a couple of advantages:
- It uses responsive design, which will make the site easy to read on mobile devices as well as larger screens.
- It’s already tested for browser compatibility! This is great because I don’t have a PC or Linux machine (yet) to test the site on, and from what I understand the various online services that do it for you are not very accurate. It would be good to test it anyway once it’s complete just in case, so I’m open to suggestions on ways to approach this. Perhaps this project is the excuse I need to finally install Ubuntu on my Mac, but I’d prefer to avoid Windows if at all possible.
I’m also hoping to survey current users to identify and prioritize features to add. Personally, I’d like to find a way to integrate more social media / microblogging, since blogging is on the decline and microblogging is more commonly used these days (as discussed recently by Stormy Peters). I am also interested in finding ways to enable the users to interact with the content in a way that helps generate more discussion. Perhaps something like Reddit’s up-voting system where readers can identify which posts they found most interesting/engaging/useful to help other readers quickly choose which articles to start with if they don’t have time to read all of them in the feed.
Do you use one or more Planets? If so, what improvements would you like to see?