as i look through the issues on github i have come to realise there is some form of disorder in how we are handling issues and i also following the discussion on yesterday’s call, contributors may continue clushing;
Some the contributors have been assigned more than 1 or 2 issues, this is creating a time lag to complete some issues making it slow to find solutions, yet there would be another contributor who would be much interest in the issue and then saves us much time
Owing to yesterday’s call i seem multiple poeple working on the same issues and all will push fixes with diferent conventions yet some fix. i feel this is a bad practice coz we are supposed be assigned an issue for you to work on it and if you raise an issue and have a solution for please do create a pr with the fix attach it to the issue then wait for review so as to avoid duplication of your work and also having the community to decide who’s work should be merged
Could we have contributors be limited to either one or 2 issues and unitll they are done with such they should they be assigned another
could we also findway of assigning contributors issues promptly i do see only @Moses_Mutesasira@Herbert are authorized, how can this be done more efficiently
i think if we i have a systematic way of handling issues and pullrequest this would help cub confusion and also be able to make this patform a better experince for all contributors
@segujja_joseph duplicate prs are surely creating issues for the contributors
The solution I can think of is that contributors who open a issue can specify that would they be working on it or is it open for others to work I would also encourage contributors that if they find some bug or issue sometimes they can allow others to work on creating a inclusive environment
Plus another thing to be mindful of, if there are multiple issues you have pinned up, it wouldn’t be wise to wanna work on them all by yourself
The key here is to raise an issue so that we have a collabrative community to work on it. otherwise you’re defeating the purpose of open source and those specific issues will take longer time if they are worked on by one person than sharing them in the community to be completed in the shorten time possible
does this make sense @Vishal_Sharma@mherman22@Herbert@Moses_Mutesasira
hello Community, trying to resolve some marge cnoflicts, but I am getting something like this here , seems it requires admin rights to rectify, is it so ??
@tasksolver you don’t have to worry about that CI check if you have resolved the conflicts already. If any admins go through the PR then they will be able to notice that “there was merge conflict but it is resolved now” and working about that “Merge Conflict” label that will go off on the next CI CD check run.