wemake-services / meta Goto Github PK
View Code? Open in Web Editor NEWHome of Repeatable Software Development Process
Home Page: https://wemake-services.github.io/meta/
License: GNU General Public License v3.0
Home of Repeatable Software Development Process
Home Page: https://wemake-services.github.io/meta/
License: GNU General Public License v3.0
This task looks like a average task you will receive from us. But it's scope is bigger than usual, since we want to see as much skills as possible.
We need to create a third-party service to list user's Github repositories.
So, the process is:
We also want to know the author of this service. Please, provide a link to the source code on the bottom of the page in a form of: Created by <link-to-your-account>, source code: <link-to-the-github-repo>.
Fill free to use any tools you like (minding the license). But, note that you are limited to the platform.
If you are applying to python
position it would be very strange to submit a js
solution.
This should be 100% working and deployed service. You should provide a live link for us to browse it.
Time estimated: from 2 to 3 hours
If it takes more than that, well, I guess you are doing something wrong.
That's how we work internally, maybe it would be helpful: http://wemake.services/meta/employees
We will need style guides for:
python
js
elixir
Listed in priority. And maybe some other languages as well.
I guess wiki
is a good place to store this kind of information.
Examples:
It should include:
editorconfig
setupwakatime
setupdocker
setuppython
setupWebsite is not the right format for our meta.
Redirect old urls to the wiki.
There are several dealbreakers for us:
Also they are different for:
They should be specified.
That's just an list of some principles I don't want to forget about. This issue would be closed after some uncertain period of time.
I need to specify what steps I should complete each time starting a new gitlab
project.
Ideally, we would need a script to handle that. See gitlab-form
. Or other tools. Platform is not critical.
How should we track and bill research tasks?
They happen quite often. And can take a lot of time without writing code.
As for me, each research must end with a document:
@izomeraza what do you think?
Right now we only use spend
micro-command to set spent time on merge requests.
As a result issues do not have any spent time. So, we need to fix that.
There are possible three ways:
Also, this task is related to the #32
We need to create a list of things we punish for.
We also need to specify how we punish in each of these situations.
We need to create the document for closing a project (ltd)
I have missed one very important step: initial commit.
It should be documented.
We need to specify how to work with issues:
@valerievich wrote:
- несоразмерные шрифты “Working with the client”, “Hiring”, “Development process” с ссылкам в этих подразделах. Либо можно вправо сдвинуть ссылки контента, чтоб обозначить вложенность (я вообще не сразу заметил, что это группы ссылок, и решил, что в кучу свалены материалы относящиеся к работе с клиентом, хайрингом и процессом разработки);
We need to fix that.
Right now we are using a custom semi-automated process to generate invoices and reports for the clients.
There are tools like http://gitlabreports.cosango.com/ which make it very easy.
We need a custom solution to generate reports easily.
Maybe it should be a part of https://github.com/wemake-services/kira workflow.
We need to define, what means to "do" something.
When your task is done? So, when should you receive your payment.
Just like in scrum
: https://www.scrum.org/resources/scrum-glossary
I guess "TOC" should be opened by default.
It would be a github browsing tool.
Advantages:
Each page should contain from 1 to 3 of the most important quotes.
It should be located in the logical places in the text. It may be a duplicate, but it maybe just a single quote.
You should use >
for quotes in .md
files and <blockquote>
in html
.
We also need to list keypoints, inspirations, books.
Maybe some videos too.
Our git
workflow is very simple yet powerful.
We need to create a special page for it.
Things to cover:
master
branchissue-*
branchesIt would also be nice to create a name for it.
Right now it is not clear enough for our future clients what methods we use to manage our porjects.
There are two limitations:
It is not possible to fulfill both limitations at the same time.
So, we must clarify what is more important in different situations.
Dependabot couldn't find a package.json for this project.
Dependabot requires a package.json to evaluate your project's current JavaScript dependencies. It had expected to find one at the path: /package.json
.
If this isn't a JavaScript project, or if it is a library, you may wish to disable updates for it from within Dependabot.
You can mention @dependabot in the comments below to contact the Dependabot team.
Right now we don't convert rates. By we need to.
We need to show prices in rubles as we do now, but to convert them to dollars on hover.
We need to specify:
Right now I have seen some outdated block, which should be changed.
I don't have the exact list, since I did not make any notices by myself.
Please, @mariamyzz take care of them.
Make sure it is possible to use heatmap and collect user interactions.
Why do we need that:
There are several meta workbooks I would like to mention:
Now it is just issue-
.
Right now our "GitLab Configuration" docs are missing "Deploy keys" step.
Right now auditions do not work.
It is impossible to measure the cost before-hands.
Let's consider pay-per-bug payment method.
We need:
Some invalid tasks may appear:
So, this task should be:
[Invalid]
Only architect can close such issues. Matrix should also be updated.
Specify, that tag creation is limited.
Tags starting with v*
are reserved.
It is better to have one source of truth. It is a website in our case.
This readme should have:
My personal opinion that styleguides should not belong here.
Reasons:
So, I think, that they should be removed.
we don't tend to devote mush time to educate
mush
job-application.md
We should pay other developers for finding bugs.
There are too kinds of bugs to be found:
The price will be counted in minutes of the developers rate.
If developer's rate is not available, then we should use 2000
rubles for calculations.
Security bugs should not be publicly available. To collect them there are two ways:
It should be structured as a directory.
Ideally, it should also have links between different processes in the different files.
Can you provide please the proper examples of "Completing a Feature" from https://github.com/wemake-services/meta/wiki/Closing-issues. It would be nice to show the steps itself on example of some issue ,to avoid misunderstanding (e.g the way to create a proper new branch name) .
Right now we have everything mixed in the docs: some basic theory, our ideas, practical todos, specific tools and settings.
We need to separate that:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.