I will be in the process of revamping the issue list on Github over the next few weeks.
My intent is to make a list of issues which are described well enough to encourage first time code contributors.
Please feel free to invite anyone to THIS forum under THIS topic whom you might think would like to join the discussion.
thank you @Grace @slspencer @schwowsers @Douglas @KeithFromCanada @ladysinaz
@Krolich I saw your discussion with @Grace of the multisize table. That is a great example of the type of thing that would make a good new feature and which should be added as an issue on github. can you create a new github issue and just give it a minimal description (ārevamp multisize table featureā) and we can discuss it on the original topic where you were with Grace.
I am about half way through (starting from the end of the list - oldest issues first) looking through the issue list and assigning some labels to categorize them. I have a partial list that I need to discuss with @slspencer. These include the following:
I have questions on whether these are still valid, should be closed, or I do not understand the description.
Due to work pressures Iāve not been in a position to push forward much with the pattern cloud. I did start work on some web services to push/pull patterns directly, rather than having the user save them to files and open them manually. There didnāt seem to be much point in progressing this without an indication that the application side would be changing to make use of same.
In essence, what I envisage is:
Clearly this needs to handle measurement files too.
If we had some suitable publicly shared templates then I would suggest that the ability to start a new pattern from a selection of cloud hosted templates would be a useful first step.
@MrDoo thank you so much for your response. I will probably close the old issue and write up a new one. I will start with what you said in this message and try to state it in such a way that it can be tackled by a contributor. I agree with you on the issue of publicly shared templates. I will attempt to describe such a template in a way that we might attract someone to help create some. If you have any thoughts on a description of template I welcome them.
There didnāt seem to be much point in progressing this without an indication that the application side would be changing to make use of same.
I will try to make it easier for a potential code contributor to see where they can help.
I agree it would be frustrating to continue to make progress in a vacuume. I have decided not to wait until my life gets calmer and just contribute what I can, when I can. I have spoken with @slspencer and will continue to do so in person when she and I can span the 40 miles that separate us. (When she is not traveling and I am not either, which cuts it down to a few days a month). I appreciate you hanging in. I still believe the Seamly2D project is the best option for many target user audiences. I intend to keep using it and for a time, I will help to make it better.
I have begun the process of adding ālabelsā to issues on the github issue list. This is primarily for the purpose of being able to easily sort the issue list. @slspencer I welcome your input or anyone elseās input on the subject of whether I have or have not chosen wisely in the types of labels I added as potential sorting tools
if you notice the label āquestionā it means that I, Kim, am not able to parse the issue description well enough to be confident how to deal with it (as of the week of Oct 23 2018)