Topluluk Talep Anketi/İyi bir teklif nasıl oluşturulur

• Ana
• Bize yardım edin
• SSS
• Results

Bir teklifi iyi yapan şey nedir? Bu talimatlar, tekliflerin tamamlanmak üzere seçilmek için en iyi şansa sahip olmasını sağlamak içindir.

Topluluk Teknik Ekibi faaliyet alanı dahilinde

Teklif, aktif Wikimedia editörlerinin teknik ihtiyacı hakkında olmalıdır. Mühendislik çalışması gerektirmeli ve bir politika veya sosyal değişimle ilgili OLMAMALIDIR.

Topluluk Teknik Ekibi, eğer teklifleri reddederse

Mühendislik çalışması gerektiren teklifler şunları içerir:

Yalnızca "teknik" düzenlemelerle ilgili olsa bile (şablonlarda, modüllerde vb.) Wikimedia Foundation ekiplerinin planlarında zaten var Geçmişte Topluluk Teknik Ekibi veya diğer Wikimedia Foundation ekipleri tarafından reddedildiyse Wikimedia Foundation ekibinin üzerinde çalıştığı bir özelliğin kaldırılması veya devre dışı bırakılması için çağrı

Wikimedia projeleri için araçlar yapmak Desteklenmeyen önemli araçların işlevlerini belirleme ve iyileştirme Bu araçların daha iyi kullanılabilmeleri için daha iyi belgeler oluşturmak Kullanıcılara zaten yaptıkları şeyde yardımcı olmak için araçlar, botlar ve sihirbazlar oluşturma Wikimedia projeleri için araçlar yapmak Varolan araçları ve botları daha fazla proje üzerinde çalışabilmeleri için değiştirme Topluluk tarafından yazılan çok kullanılan kodun (araçlar ve kullanıcı komut dosyaları) MediaWiki yazılımının bir parçasına dönüştürülmesi

Bir yıldan az bir proje, bir hatadan fazla

The Community Wishlist Survey is limited to the capabilities of the Community Tech team.

The team is grateful for "big ideas" for the Foundation and doesn't ignore them. However, some proposals require a dedicated team other than Community Tech.

These proposals will be moved to a separate page and will not be voted upon. Later, the link to that page will be shared with other Wikimedia Foundation teams.

Örnekler:

Make SecurePoll accessible through local wikis (too large) "POV Detector" for articles (too large) Make a mobile application for Wikivoyage (too large)

Watchlist item expiration (large-ish) Ping users from the edit summary (ideal size) Copy and paste from diffs (small-ish but not too small)

Pick one specific problem and describe it in detail

Provide context around why the problem is important for users. A good proposal explains exactly:

• Sorun şu ki,
• Who's affected by it.
• Add screenshots, links, and talk pages detailing the discussion about the problem space, if possible.

This will help Community Tech to understand where to begin their work.

Don't just say that "(x feature) is out of date", "needs to be improved" or "has a lot of bugs". That's not enough information to figure out what needs to be done.

Proposals may be submitted in any language. Community Tech encourages the volunteers to translate them so everyone can read and vote on it more easily. Read more on Review phase.

Örnekler:

Add Better Bots (not precise enough and reading between the lines, too large) Make wiki easier for most people (not one problem, but a principle for a lot of changes) Implement Artificial intelligence (not one problem, but a principle for a lot of changes)

Better diff handling of paragraph splits Show all active sessions Use Wikidata to improve search

Çözüm bulma konusunda endişe etmeyin

You don't have to suggest ways for resolving the problem. It will be the Community Tech task to find solutions.

Prescribing the solution can sometimes be a constraint. For example, voters could mistakenly support a solution that later in the year could turn out to be impossible to build, and Community Tech would solve the problem differently.

Examples:

Tags (ala evernote, searchable, catagorizing) (no information on the problem)

Bulk upload program (no information on the problem)

Diğer topluluk üyeleri ile konuşun

You may want to bring attention to your idea, and be part of a conversation about the idea happening elsewhere. Gather feedback and share the proposal. You can do this early on, before the voting phase. This way, contributors can know about the problem and remember to participate and vote for it when the time comes.

Also, see our promotional materials. You may use them.

Avoid proposals that were declined in the past

Here's a list of some of the projects that got many votes. Community Tech was committed to work on them but had to decline them. It is unlikely, if not impossible, that the team could work on them this year.

Anket basımı	Rank in the results	Projeler	Açıklama
2019	#2	Gece modu	Overlaps with another team's project. The overlapping project is Desktop Improvements. Daha fazla bilgi.
2019	#6	Put mw.toolbar back	The issue had largely been resolved without any Community Tech intervention. Also, it is the Community Tech policy not to undo changes made by other teams. Daha fazla bilgi.
2019	#8	Article reminders	This is too technically complex. Also, it would have to be done by another Wikimedia Foundation team. There are other ways to see the same result. Daha fazla bilgi.
2019	#10	2FA available for all concerned editors	This is too technically complex. Also, it would have to be done by another Wikimedia Foundation team. Daha fazla bilgi.
2017	#6	Article Alerts for more languages	This is too technically complex. Also, the Community Tech is not able to build and maintain such a tool. Daha fazla bilgi.
2016	#1	Global araçlar	This is too technically complex. Also, the Community Tech is not able to build and maintain such a tool.
2015	#3	Central repository for gadgets, templates and Lua modules
2015	#6	Allow categories in Commons in all languages	Overlaps with another team's projects. The overlapping projects are Structured Data on Commons and Structured Data Across Wikimedia.
2015	#4	Cross-wiki watchlist	This is too technically complex. Daha fazla bilgi.
2015	#8	Global cross-wiki talk page	Overlaps with other teams' projects. The overlapping projects are Flow/Structured Discussions and Cross-wiki notifications. Daha fazla bilgi.
2015	#10	Add a user watchlist	Used in bad faith, this tool could make it easier to harass users. Daha fazla bilgi.