15.03.2014 – Michał ‘rysiek’ Woźniak: Free/libre/open Licenses

Free/libre/open licenses – licenses for works (like software) granting users the four freedoms:

  • freedom to use/run for any purpose;
  • freedom to modify, improve, create derivative works;
  • freedom to publish and pass the work further;
  • freedom to publish and pass further the modified/improved/derivative versions. There are two kinds of such licenses: copyleft and not-copyleft.

Examples: GPL, BSD, MIT (for software); CC-By, CC-By-SA (for other works)

Copyleft licenses – licenses requiring that derivative works (like projects based on a given code/library) are also similarly licensed.

Proponents point out that such licenses are better at protecting and guaranteeing the four freedoms to all possible users of a given code/project/work, by making it impossible for anybody to “close” a derivative work.

Hence, every user of every single derivative work has their four freedoms, regardless of whether they use the original work or any derivative of it.

Examples: GPL license family; CC-By-SA

Non-copyleft licenses – licenses that do not require derivative works to be published on a similar license. Proponents point out that they give more freedoms to direct users of projects using such licenses, as it

allows them even to make a “closed” derivative projects and works. Examples: BSD, MIT; CC-By

Free/libre/open-source software – software licensed under any free/libre/open-source software license. Free/libre/open resources – resources (like sounds, graphics, video) licensed under free/libre/open

licenses for artistic works.

Lists of licenses considered free/libre/open

Open-Source Initiative endorsed licenses: http://opensource.org/licenses

Free Software Foundation licenses: http://www.gnu.org/licenses/

Comparison of free/libre/open-source software licenses https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses

Creative Commons free/libre/open licenses for artistic works: http://creativecommons.org/licenses/by/3.0/en/ http://creativecommons.org/licenses/by-sa/3.0/en/

Rider o wolnych licencjach / Free/libre/open licenses rider, autor/by: Michał “rysiek” Woźniak, 2013-2014; na licencji / licensed under: Creative Commons – By attribution – Share-alike – 3.0 PL http://creativecommons.org/licenses/by-sa/3.0/pl/

11.03.2014 – Alexey Sidorenko (Teplitsa): What a Good Hackathon Project Should Have (Practical Checklist)

A practical checklist for the Central Open Data Hackathon

During the Central Open Data Hackathon every participant will have about 20-24 hours of effective work (unless, of course, you’re an android, zombie, or both and you neither need to sleep nor eat).

This is quite a short period of time and the competition is quite intensive. Use your time wisely. We’ve prepared a short checklist (below) of what a good project should have in order to succeed. We’ve suggested the time needed for every stage of the process (of course, it’s up to you to manage your time).

  1. Prepare. Think of the tools, datasets, software you might need before the hackathon. Learning about the technologies needed for your project – is a good homework to do. Browsing Internet during the hackathon looking for the solution – isn’t necessarily the best use of time 😉

  2. Talk. As soon as you get to the Hackathon, don’t dive into coding. Talk first. You will need good understanding of the problem, which the your project aims to solve. Try choosing small problems. [30-60 min]

  3. Talk more. You will also need good understanding of the target audience. Who will be using your project? Try creating a persona (a sterotypical user, model of a person, ideal example, e.g. John Smith, 45-year old clerk with a family and 10 years of credit to pay off) for whom you’ll be creating your project. Refer to this imaginative persona when making a prototype. If you think you can manage several use-cases try developing several personas. [30-60 min]

  4. Develop a prototype first.  In the beginning, it’s easier to create a prototype than code. You can use sheets of paper, PowerPoint, Moqups.com or other specialized tools for that. [5-6 hours]

  5. Then Develop Minimum Viable Product (MVP). After you and your colleagues agree on the prototype, start coding. Coding is a time consuming project, and you know that. Therefore, code a MVP – something that resembles the function you plan to develop. It doesn’t have to be perfect but it has to solve the problem you’ve explored in pt.2. If you don’t code yourself, you can think of promotion or other use-cases or make a nice presentation. [10-12 hours]

  6. Create a presentation of your project. Prepare 5 minute presentation. Ideally, it’d be great if you could record a promo-video or an animated infographics (try using moovly.com or visual.ly) about your project – it is fun to watch such videos [1 hour]

  7. Keep your files organized. Upload the MVP to the code repository (GitHub or BittBucket), send the organizers the link to it and the powerpoint presentation; save your prototype – save it for your grandkids 😉

Good luck and see you at the Central Open Data Hackathon!

Alexey Sidorenko is the director of the Russia-focused project “Teplitsa. Technologies for Social Good,” public education project aimed at developing cooperation between the non-profit sector and IT-specialists.

06.03.2014 – Alicja Peszkowska (TechSoup Europe): Don’t Ruin Your Weekend With Homework. Advice for Civic Activists

Hackathons are a great way to collaborate with a team of various talents to achieve a specific goal. They are not marathons, but rather sprints: 48 or—in this regard—16 hours to come up with a working  prototype is not that much. Thus, in order to win, you need to know where and how you are running to. Some training beforehand along with a pair of special shoes will do too… (more…)

Chris Worman (TechSoup Europe): Don’t Ruin Your Weekend With Homework (Notes for Coders)

Hackathons keep happening in spite of a rather mixed reputation – ranging from awesome-super fun-sexy to a complete waste of time. They can be either. The good news is which experience you have at the ceehack.org is largely up to you.


18.02.2014 – Central Open Data Hackathon in the Media // Central Open Data Hackathon w mediach

Nie możesz doczekać się Central Open Data Hackathon? Śledź hashtag #ceehack14, dołącz do wydarzenia na Facebooku.


Can’t wait to participate in the Central Open Data Hackathon? Follow the hashtag #ceehack14 and/or join us on Facebook page of the event.