One bugfix: don’t break whole timeline widget when there are TODOs without due
New feature: stop using dots (.) for usernames, use underscores (_)
This was an interesting issue: since we rely on some Ruby software on the SWC
website, we can’t have dots in filenames (they’re treated as parameter access
operator, for example: banaszkiewicz.piotr is piotr parameter on
banaszkiewicz object). But we have filenames that correspond to usernames in
AMY. So it was necessary to drop dots and switch to underscores…
Unfortunately, due to the way we have our project laid out on GitHub, some of
the features implemented for v1.4 before this feature were included in the
deployment; I will still put them to v1.4 section, though.
The biggest highlights of this month are definitely:
first approach to the new API
There were also some essential features, but not much. In v1.5 there will be
a lot more.
We had to programmatically fix/complete some of our records:
historical events on production server were assigned an administering
organization (that’s the one responsible for taking care of the workshop
new DC instructors were added: anyone with a special note or anyone who
taught at DC workshop now has a DC instructor badge.
Looking at the
list of issues
for this release, it seems like many bugs were fixed. It’s true, however the
bugs themselves weren’t that big:
some fields containing numerical values were switched to other type of fields
to prevent slider from appearing; the background for this issue was that
when scrolling through a page with form, on MacOSX people would accidentally
change values of numerical fields,
generation of initial revisions was added to the process of creating a fake
database for development use,
some types of events (stalled and unresponsive) were kicked out from
some invoice options were changed to remain consistent with the rest.
As usual, we hit a fair number of new features for AMY:
Person model is now able to store person’s occupation and ORCID code,
events can hold links to survey results (pre-workshop for learners and for
instructors, post-workshop for learners and for instructors, and long-term
API call for getting members list is now for logged in users only, and
returns members’ usernames too,
merging events: with option to select fields from either of events, or (in
some cases) even to combine them together. The underlying code may be
reused to fix persons merging,
workshop issues page now allows to filter workshops by assigned admin
move most of reports to the API; 3 reports now present a graph for easy use,
1 report was requested to be moved to API, and 1 new report was requested
(and I made it in API),
API: new structure. It’s using hyperlinks between resources and allows to
view and filter for example people associated with specific events,
slow tests were fixed (we gained probably around 10s on whole test suite,
even though about 10-20 new tests were introduced); now it’s time to speed up
Greg added two new badges to the database: maintainer and trainer; I made
sure to allow for editing badges via Django Admin interface, and also added
these new badges to the fake database command,
Greg also added a new command for getting list of people who should be warned
because their instructor training was about to close,
meanwhile I added a command for displaying report about instructor training
The next release may be last one made on such regular basis. The reason for
this is that in March I start a new academic year (Masters!) and I know it will
be very hard; what I don’t know is if I have time to work on AMY this much as
in previous months.
Therefore there are multiple important features we want to implement in the
v1.5 release – look for
the “essential” issues.
I’m studying Automation Control and Robotics, a major that doesn’t say
clearly what a person would do after graduating it.
From time to time I talk with people who either think I’m studying programming,
or that I’m going to build robots in the future.
What is Automation Control and Robotics?
Most people don’t know what automation control is, so they focus on the part
that sounds familiar: robotics. They automatically assume I’ll be building
Well, I won’t.
My studies concentrate on things like control systems (think of it as
control theory, electronics,
specialized electronics (FPGAs, embedded systems, assembler programming,
industrial-class robots), leverage of
in industrial process identification, computer vision,
As you can see, I was mostly balancing between engineering and very specialized
computer science. There really was very little robotics during my Bachelor’s
What can you do after graduating?
I like to call it: engineering.
People graduating automatics control and robotics are vast-minded, and ready to
work in pretty much any engineering field that has something to do with
we can set up wind-turbines
or air control systems
or nitrogen refill systems
or fine-tuning of power plants
or building assembly lines
There are thousands of options, all different kinds of industries.
Do I enjoy these studies?
Contrary to many of my friends, I do enjoy studying automation control and
robotics. I learned a lot of engineering- and maths-related subjects, and
I have hopes for a great work in future.
the same API gained a new endpoint used for generating list of
current members of Software-Carpentry Foundation; this is in no way
official list of members, but it can be used to help determine who’s
eligible (credits for this one go to both Greg and me since I
finished his pull request),
it’s now possible to search in events’ URL, contact, venue and
2 new options for invoice status were added (not invoiced for
historical reasons and not invoiced because of membership),
more places (workshop issues, and on each workshop without
attendance data) to send “Give us attendance figures” emails, more
people to send to,
profile update requests can now be edited by admins.
There’s number of issues scheduled for
v1.3 release, and
there will be others added to that list. The problem is that December
end of my semester,
one huge exam, a couple of smaller tests,
deadline for my BEng. project and thesis.
So total time spent on AMY in December probably will be lower than what
I did in November.
This is the second post-gsoc release of AMY, the workshop management
tool for Software-Carpentry. Below
you can find a release notes for version
I’m very happy to announce that development of AMY versions 1.1, 1.2 and
1.3 is supported by prof. Ethan White.
Thanks a lot!
Can the low number of bug fixes mean that AMY’s getting mature? I hope
Small typo in README.md fixed.
Logic for displaying uninvoiced events was fixed so that events
marked as uninvoiced but without any admin fee do show up on the
Fields layout on the profile update request details page was changed
to avoid confusion.
Better wording in email request to workshop hosts for attendees
New switch for Open/Closed requests (both profile update requests
and workshop requests). Admins will be able to look up dismissed or
“Recently changed” log was moved to a separate view so that it
doesn’t clutter the dashboard.
Some objects (events, hosts, persons, airports, tasks) are followed
Thanks to that fact we can now show who+when created any of these
objects and who+when last modified it.
Each event marked as “uninvoiced” can easily be invoiced by the
admin thanks to the new “Invoice” button on the event’s details
New report: people who have been through instructor training but
Self-organized workshops can now have a “self-organized” host.
New report: show how often instructors teach.
Admins can mark events as completed and throw them out of the filter
Big: events can have multiple TODO items associated with them.
There’s already a big pile of things to do for the
v1.2 release. I
can guess that only a number of the issues will be fixed. It’s good,
because otherwise there would be nothing for me to do for v1.3. :)
That was a looong ride, but we’re finally here! AMY is mature enough to
be given the v1.0
This will be a joined release notes to multiple
Greg Wilson has worked on the “problems” page: switched its layout
to 3-column, added better email messages, etc.
He also extended our API to return airport’s country.
I hot-fixed an issue with creating M2M with intermediary model in
model forms (basically impossible, we have to do this manually).
This release adds workshop request forms and profile update request
form to AMY.
I hot-fixed a bug with settings: we should load more email settings
from environmental variables in order to use emails from Django.
I added a new country: ‘Online’ (for international / online events,
like some Instructor Trainings).
The dashboard was changed to show not only upcoming, but also
ongoing workshops (in the same column).
Greg added some helper commands to report inconsistencies in PDF
certificates for instructors.
He also removed old command used for checking AMY’s database against
SWC site’s archive. Site has moved to use AMY’s API, so the archive
was gone and the command was made redundant.
I updated check.py script (used for checking workshop settings
correctness) from workshop-template repository.
Greg cleared up titles of forms introduced in v0.9.5.
I split these forms’ templates and added SWC and DC logos to them.
Bulk-uploaded CSVs with entries that contained empty rows (for
example: ,,,,,,) were treated as correct, but not anymore.
“Artificial” country European Union had been removed and was brought
back since some hosts were using it.
API now returns website URLs to events instead of original URLs.
We have a new database for development use (I need to switch to
fixtures some day…).
I changed the way AMY handles event URLs:
admins cannot use GitHub repository URL for event’s URL
migration was used to change all URLs to website-URL format (if
I also fixed import/update from URL feature to auto-select
country if possible
…and to auto-use correct website URL instead of repository URL.
AMY auto-counts event attendees if provided with a list of attendees
(for example via bulk-upload).
External links now open in new tabs.
Now there are more options to Event.invoice (for example with reason
for lack of invoice).
New remove awards functionality.
I asked our admins what they want to see next in AMY and I received very
nice feedback. You can see all requests in v1.1
tag on GitHub. It’s
scheduled for the end of October (but you can expect some delays :) ).
With a week of delay (3 weeks after v0.8 release), I finally released
AMY v0.9 today.
The list of changes for this release doesn’t contain one big thing I was
hoping for, but it’s still decent.
This is also the last release that (partly) took place during Google
Summer of Code 2015.
Google Summer of Code 2015
I’d really like to thank everyone who helped me during this Summer:
Raniere Silva for keeping eye on the participants’ reminders and for
so many friendly chats over these months
Greg Wilson for mentoring me and for lots of enjoyable meetings
W. Trevor King for introducing me to some very advanced git methods
my application’s users: Amy, Giacomo, Maneesha, Tracy and others,
for providing me with excellent feedback.
This was incredible Summer; I learned a lot and had so much fun. That’s
great to see that we’ll release AMY
v1.0 soon as a
wrap up of 4 or 5 months of work.
Okay, back to the change log.
Some workshop URLs weren’t translated between repository and website
versions. This is now fixed and every workshop with one of these
links will automatically display the other link as well.
It happened that users put whole links into Host.domain (in the
form https://domain.tld). This caused errors in many places where
we wanted to display link to that Host. The issue is now fixed:
users aren’t allowed to put protocols or trailing slashes into
Some management commands were broken due to the fact that we
switched underlying methods to use API endpoints, but we didn’t
change the commands themselves.
This release was focused on getting permissions sorted out and adding
read-only access to people from Software-Carpentry Foundation Steering
We had to cut out the another exciting feature: workshop requests,
profile update requests. The Pull Request for this feature is very big
and we’ll release it in
in the next week.
AMY v0.7 was
released today. You’ll find list of changes below.
This release contains surprisingly few changes, and the development
seemed slowed a little, but that’s not a bad thing: Greg’s moving to
Europe with his family and I’m going from time to time on 2-day trips
This time I start with bug fixes.
Check if event’s starting date is earlier than it’s ending date.
Ensure event’s administrative fee and event’s attendance are both
This release was themed “fixing
representation in the database”, and I claim success!
The change was rather significant and required me confirming ideas with
Software-Carpentry administrators and Steering Committee.
Rename “Site” to “Host”
Previously event’s host was incorrectly named “site” (ie. location).
Rename “organizer” to “administrator”
Event.organizer field was mostly unused and no-one knew it’s real
purpose. By changing it to “administrator” we now have a place for
our administrators to mark events they’re working on.
Filter by administrators on the “All Events” page
We can filter by Host, we can now also by administrator.
More location fields for Event
Workshops that have a public website (most of our workshops does)
contain standardized location data we didn’t previously collect.
This was required by some other features.
contact field for Event
Additional field we didn’t collect in the past.
I switched the Travis-CI server to use fast Linux Containers.
Testing time dropped from 1.5min to 45s.
It’s possible to select multiple countries and preferable gender on
“Find Instructors” page.
Lookup instructors closest to the event’s location
From event’s details page administrators can quickly go to “Find
Instructors” and search by latitude/longitude.
“Update from URL” functionality
This works in a similar way to “Import from URL” from v0.6.
Plans for v0.8
Greg wants v0.8 to store demands for Instructor Training in AMY.
Event details page will show link to the Eventbrite’s event page
instead of sole key ID.
Quick link for new airport page
Accessible from “+” dropdown menu.
Auto-fill end-date on event form
Setting a start-date for an event will set-up an end-date (+1 day)
automatically (most of our workshops lasts for 2 days). The
auto-fill won’t happen if user put something into end-date field.
2-column layout on person-details page
First column contains awards and tasks, while the second column
contains knowledge domains and lessons person can teach.
Facelifted Find Instructors page
Full-width layout, filters in sidebar, no setting of “wanted”
instructors. Using GET for filters application instead of POST as
Ability to add tasks for person from their edit page
Now admins can not only assign awards to specific persons from their
edit page, but also tasks.
Tabs on person edit page
Because of using 3 forms and 2 listings on the person edit page, the
split was necessary. The first tab contains original person edit
form, the second tab contains awards and award-form, the third one
contains tasks and task-form.
Another switch to full-width layout. Confirmation page for
bulk-upload will now show what happens with specific entries (“will
be created” or “it’s already in the database” kind of thing).
Lessons sorted by default
Lessons will appear in alphabetical order in Find Instructors filter
and also in “lessons” column on that same page.
Importing event from URL
Admins can pre-fill event create form with data from workshop page.
Improved “failed to delete” page
Thanks to one small discovery, a big and ugly chunk of code was
replaced with almost a one-liner.
Display of tasks
Tasks now show links to events and persons.
Eventbrite event ID name change
Previously it was ‘reg key’, now it’s clearer.
Better fields in airport form
“Airport name” instead of “Fullname”, “IATA code” with link in the
“help_text” instead of “Iata”.
Better list of tasks on person-details page
These tasks now contain links to related events and clearly indicate
roles a person has.
Searching for “firstname lastname”
Searching for “Piotr Banaszkiewicz” now works!
Enforced uniqueness for event slugs
Having two events with the same slug resulted in a crash, so we
decided to enforce uniqueness for event slugs. This not only
prevents the bug from hunting us, but also prevents admins from
adding events with slugs that are already in the database.
Awards will prevent events from deletion
If there are some awards that point to specific event, that event
will not be deleted.
Plans for v0.7
There are two things that I want to work on for v0.7 release.
I want to add develop branch and set it as the main branch for the
The rationale for 1. is that I had to make two minor releases to v0.5
when we already had features for v0.6 merged to the master. If we had
only kept stable releases in the master
I’d not have that problem.