Proposed change

GH has introduced "discussions". For me it looks like just an issue, but under another title. Should we convert the issues into discussions?

Though it should be checked, if it is possible to control discussions templates.

Proposed change

Making an approachable GUI for this community

Motivation

Hi there!
First of all just for context, I just googled
"Suggest idea open source" and got here.

So let me thank you,
I was developing an idea about building an app for suggesting open source ideas.
So thank you so much for already making this! It's one more project checked on the list :)

Anyways I hope to get more familiar with the current OSI platform (GitHub issues oriented) soon but I believe that this projects deserves a better front-end. Going to the site is just a never ending list, it should be more user friendly, modern looking, with searches, categories like new, tending, favorite ideas, and so on. All in a nice visual GUI. Maybe even users, and "friend suggestions" based on coming interests/follows/searches. And of course putting this all in a pretty little app will be the best. I think that any UI improvements that will make osi more approachable will be enriching to this community.

Proposed implementation

To be honest I'd start from wix, or Django or something that will be a quick major change in the UI, then work on app design and architecture

Little Disclaimer, if you do have an app/better site/ or something and I don't know about it, apologies (put it in the upper readme like you're site). And if something is on the pipeline I'll be happy to get a referral so I can contribute where I can

Hope to hear more! Thank you!
Have a great weekend!
Tami

Proposed change

Implement a system that allows community to vote on ideas.
Something that would function similarly to what UserVoice does (or PHPBack since we are doing FOSS)

Motivation

So that good ideas get voted up and not get lost among the other ideas.

Proposed implementation

For example, have users voice their support for the idea by adding 👍 reaction to the idea, and then have tags for [+10], [+50], [+100], etc. and apply those tags to ideas (issues) in close-to-real-time (maybe have a bot to watch the 👍 and apply tags).
That way users can filter or effectively sort the ideas by popularity.

(actually, by writing this I found out that you can actually sort ideas by reactions by adding sort:reactions-+1-desc to the search query)

Originally form @dannycolin in open-source-ideas/ideas#76

Proposed change

Add programming language tags to issues and also show them on the website

Motivation

This would help people to filter project ideas by programming languages.

Proposed implementation

• Create a set of tags with the same color that looks like language : JavaScript
• Show them on the website. (btw where's the website source code, if we want to help?)

Suggestions, ideas are welcomed.

Proposed change

Add a criteria to indicate whether a project has already been implemented in non-FLOSS projects.

Motivation

Increase focus on projects that really have no functional alternative anywhere.

Proposed implementation

Adding the following labels : no alternative, premium, freemium, freeware

Orignally by @KOLANICH at open-source-ideas/ideas#55

For now the issues in this repo are marked with Little work, Medium work, Much work and Beginner, Intermediate, Advanced labels.

But what is Much work ? Is developing an app in the way "take existing libraries, make them do their tasks and return the results, compare the results and show them to user" really so much work for an advanced engineer? I guess we need a more objective criteria of amount and complexity of the work, taking in account

• existing libraries
• libraries to be created
• development and reverse-engineering tools and their capabilities
• amount of research and requirements to the researchers (I mean here not level, but domain and specialization, if the work requires expert knowlege in different domains, it is more complex and may require more people (with competencies in differrent domains) to be finished).

Should we have an OSII logo to use on avatars and such?

One idea I had was to use the OSI (Open Source Initiative) logo (which is CC licensed) to create a light bulb.

Any thoughts, @open-source-ideas/osii-maintainers ?

(Based on the Open Source Initiative logo, not affiliated or endorsed by OSI in any way.)

Proposed change

GH Actions allow to trigger an action when an issue is added and then do something to it. Currently @FredrikAugust assigns the tags manually. It is proposed to create a script parsing the issues and assigning the needed tags.

Proposed implementation

• In the repo a yaml file containing the description of sections and tags in it is stored.

- name: Complexity
  limit: 1 # the greatest count of the checkboxes to be selected. # If more than this amount is selected, first ones (in `allowed`) are kept.
  allowed: # only these tags are allowed.
    - Much Work
    - Little work

Repetition of the sections mentioned in the file is not allowed, in this case the issue is considered invalid.

• on each issue creation or first message update the bot checks the format. If the format is not satisfied, the issue is closed.
• it then synchronises GH tags with the tags described in the file.

Originally by @KOLANICH at open-source-ideas/ideas#67

Consider moving away from GitHub due to the recent (though still open) acquisition by Microsoft and taking into account what Microsoft have made to its own websites (they (at least some of them) don't work at all without JavaScript enabled and have tracking scripts, if M$ done this (or something else unfriendly, like unfriendly shifts in privacy policy) to GitHub, I (and I guess some other self-respecting people) will have to delete my account). Also GH is a de-facto proprietary monopoly, and having monopolies is bad, so I have thought long ago about migrating to GL (which is free software, even though the company running it seems to be unfriendly (the service Gitter owned by that company uses browser fingerprinting), the fact the software is free allows people to fork the software and migrate to own (or third-party) servers), but there are too little devs using it. But now, when the exodus from GH has started, it's a good opportunity to join the movement and make the market a little bit less monopolised.

Proposed change

I'm thinking about writing a small CLI for fetching new open source ideas, as a terminal fanatic, I'm sure many others would like this happening too. However, the webhooks set for the open-source-ideas repo is not public and cannot be accessed.

I'm not too experienced with webhooks, but I believe this can be done somehow(?).

Thanks.

Motivation

Proposed implementation

Originally by @FredrikAugust at open-source-ideas/ideas#59

Project description

The current website is due for a rework (you can blame that on me, I'm not the worlds best web designer). As of now it's not really worth using, as GitHub issues is a lot clearer.

The current code can be found here if you wish to have that as a starting point.

Relevant Technology

• Web design
• Front-end web development
• GitHub API

Back-end isn't really necessary, as you can just query the GitHub Issues API.

Who is this for

Someone who knows how to create interfaces that provide a simple overview of repeated content (GH issues in this case), and preferrably someone who is familiar with front-end web development.

I'd happily help with the technical stuff (state management, working with the API etc.), but - as proven - I need someone who can do the design.

Share this on twitter/facebook/myspace/irc or any other place where someone might catch interest ;)

New project on Open Source Ideas Initiative: Rework the open-source-ideas website – https://github.com/open-source-ideas/open-source-ideas/issues/59

• Add programming language tags Open Source Ideas Initiative #76
• Migrate from GitHub #67
• Rework open-source-ideas website #59
• Develop a criteria for work and difficulty estimation #55

Proposed change

Motivation

What is considered a project to be complete?

Proposed implementation

Common for all approaches:

• A project repo is created and sources are published under a FOSS license.
• The project also has an issue/bug/ticket tracker.

Approach 1

All the goals stated in the top post are met.
Cons:

• Implementer doesn't get an immediate recognition.
• Implementer is manipulated.
• We have to track a project longer even after its discussion has move into an own issue tracker.

Pros:

• No need to decide which goals are essential and which are not, so no need in getting consensus.
• Implementer is manipulated into finishing all the goals of the project.

Approach 2

Essential goals stated in the top post are met. The project is already usable for its users and the rest of goals can be achieved by adding the features to the existing project feature-by feature.

Pros:

• Implementer gets immediate recognition.
• No need to track the project longer, it has an own issue, it makes more sense to track the non-essential features there.
• Implementer is not manipulated.

Cons:

• We have to have a consensus somehow on what is considered to be an essential feature. Though I don't think it will be a problem here.
• Implementer is not manipulated into finishing all the goals of the project.

Approach 3

Differentiate between fully implemented and minimum viable. Have separate halls of fame for them.

Pros:

• Implementer gets an immediate recognition.
• Implementer is manipulated into finishing all the goals of the project.

Cons:

• We have to track a project longer even after its discussion has moved into an own issue tracker.
• Implementer is manipulated.

So IMHO we should stick to Approach 2.

Question or proposed change

open-source-ideas is now looks like it is software centered.

But there may be projects not about software, but also about creating, sharing and acquiring knowledge, which substantial parts are real world objects (i.e. hardware) costing real money.

How are we going to treat such projects? There are several options:
a) say they are out of scope;
b) create another repo and bug tracker for them;
c) or use the main issue tracker for them, probably requires renaming and some new labels.

Proposed change

GitHub has a new feature of form-based issues.

https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository#configuring-the-template-chooser

https://raw.githubusercontent.com/pypa/setuptools/main/.github/ISSUE_TEMPLATE/feature-request.yml

(though the YAML format for template looks more like EEE , though it is easier to parse, I guess GitLab may have issues with support of it)

Motivation

Proposed implementation

https://github.com/open-source-ideas/open-source-ideas/blob/master/CODE_OF_CONDUCT.md

As of now it says "INSERT EMAIL" which is not an email format I know, so perhaps consider changing it. If wanted mine can be used, but I think a shared one for @open-source-ideas/osii-maintainers would be best.