3 ms·

Contributing seems difficult when the issuetracker is an unstructured mailinglist

• mistrial9 5y ago
  > Contributing seems difficult yes, contributing is difficult > an unstructured mailinglist the main barrier to entry is not the lack of simple issue tracker though! <rant>with something so well engineered, so visible each day to users (performance,features) and invisible to users (implementation), so portable (OS,arch) and so just .. careful.. The mental models needed to make meaningful changes to the code base, are so layered and detailed, the issue tracker is just as plain paper envelope as it can be ! If you dont know your bugs you shouldn't be here! so the gruff, take-no-prisoners engineering attitude goes .. and there is plenty of that in PostgreSQL, seems to me On the other hand, modern FOSS plus dropping boomers, relays the actual fact that no, you do not have to get the "my patch was rejected by Tom" t-shirt to participate and IMPROVE the project. Its just that, this has not always been the culture, and now, maybe there are winds of change. Every single core PG engineer today will pass away one day. PG is dead - long live PG ! yes, make the issue tracker but also, learn your bugs if you are seriously contributing at the core.
  • jbverschoor 5y ago
    Actually it is. If you want people to help, make it easy to do so. This means a structured list of what to do. There’s a todo-wiki with some links to mailing threads of years old. With unaccepted patches without explanation what’s wrong. If you want an engineer to help, don’t require him to be a PM