AllMyChanges Mission

When our project was in its infancy, it was based on the hypothesis that a changelog can be found for almost any library, and if you cannot find it, you can build it from commitmitages. But the reality was not as rosy as we wanted: either the changelog file in some ugly format would fall, then it was no longer kept, and the product was developing, then something else. And then we realized that splitting the world is not enough, we need to change it.

To change something in one moment is an extraordinarily difficult task.

Therefore, we do not set ourselves such a goal. The mission of AllMyChanges is to let developers around the world understand that ChangeLog is their way of interacting with the outside world, the same channel as a blog or a twitter account.


')
Before the advent of our service, it was difficult to compare a simple ChangeLog with a blog, since there was no way to subscribe to updates. After all, a link to the rss blog feed can be thrown into the rss reader, you can subscribe to the social profile, follow a person, and it was difficult to subscribe to library changes.

Some developers, seeing such a problem, are trying to build communication with users of their libraries or API using blogs. There they write about releases, sometimes they seal cats and other news, maybe not directly related to releases. But so few do, because to blog for each of their opensource libraries is very expensive and, you see, it's much easier
add sections in ChangeLog.md file and commit it to the repository.

GitHub, for its part, is also trying to give developers an interface for communication built around repositories. It's called GitHub Releases . It works like this: you put a git tag with a version, then, instead of adding a ChangeLog, you go to the GitHub interface and add a description of what happened for the release. To all this, you can attach some binary artifacts, such as collected under different platforms. For releases made using GitHub Releases, an RSS feed is generated, there is no other way to subscribe to project news, except for third-party services like Sibbell or AllMyChanges . True, Sibbel works only with GitHub Releases, and in AllMyChanges there is no such restriction, it works with any sources.

By the way, according to our calculations, about 10% of all projects that have been added to AllMyChanges use the release service on a githaba. That is why more recently, we supported the GitHub Releases, as another data source. They come through the narrow tube on the right:

Communication is our your everything

API developers also have a great need for a communication channel. Many of them do not want to admit it and in every possible way hide the information that and when they change in the API, but there are also good guys who are well aware that only regular interaction with users allows us to build a healthy developer community.

By the way, the same situation is now in the market of mobile applications. Many companies are now aware that release-noutsy is an excellent communication channel and begin to use them for their intended purpose, not only transferring important information about the changes in the software, but also entertaining their users. Look, for example, at what Slack and Trello developers are writing.

So, the mission of AllMyChanges is to reduce the number of guys who write in their release notes: "This update includes minor improvements" and turn away from the wall, falling asleep with a sense of accomplishment. Do not be among them, tell your users about what is happening, encourage them to subscribe to the changelog on AllMyChanges .