Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overview Speakerinnen construction sites #216

Closed
11 of 49 tasks
zaziemo opened this issue Mar 11, 2014 · 22 comments
Closed
11 of 49 tasks

Overview Speakerinnen construction sites #216

zaziemo opened this issue Mar 11, 2014 · 22 comments

Comments

@zaziemo
Copy link
Member

zaziemo commented Mar 11, 2014

Why this?

If you want to contribute, you can get an overview over the open issues. We are happy to answer your questions if you consider to help. All the issues have a link to their specification. If you want to work on an issue feel free to assign yourself.

! current bugs

1. topics, tags and references

2. tests

3. separate pages

4. performance and security

5. design and styling

6. translations

7. usability

8. search

9. features

10. other

@zaziemo zaziemo mentioned this issue Mar 11, 2014
33 tasks
@svenfuchs
Copy link
Member

@zaziemo perfect use of GitHub todo lists :) you've real got the hang of this.

@zaziemo
Copy link
Member Author

zaziemo commented Mar 12, 2014

@svenfuchs thanks ;) Do you think that is a good starting point to guide people who want to help us?

@svenfuchs
Copy link
Member

@zaziemo it is! you could link to it in the readme, in blog posts or on twitter.

@carlad
Copy link
Member

carlad commented Nov 10, 2014

hey @zaziemo i could work on:

#225 separate page for "news"
#269 footer should be on every site

and

#215 add tests for the admin unpublish and publish method
#245 add unit test: tags forced lowercase for already existing tags

??

@zaziemo
Copy link
Member Author

zaziemo commented Nov 10, 2014

@carlad great! I would be cool it if you'd work on #269 ;) If we are lucky we will fix the staging/master thing today and you can create your own feature branch derived from master.

@carlad
Copy link
Member

carlad commented Nov 11, 2014

Cool. Did you fix the staging/master problem?

@zaziemo
Copy link
Member Author

zaziemo commented Nov 11, 2014

@carlad no not yet :( But it will be fine if you work on master.

@carlad
Copy link
Member

carlad commented Nov 11, 2014

Alles klar. I will pull from master but create my own 'footer' branch.

A couple of questions:
When you say 'every site' do you mean every language version of the website?
What do you want the footer to contain?

@zaziemo
Copy link
Member Author

zaziemo commented Nov 12, 2014

@carlad I will answer that in #269

@pohameera
Copy link

@zaziemo, Hi! Your project seems very interesting. Me and my teammate @Neethusajeevan could work on:
#192 Content Localisation
#249 assigning tags to localisation
#201 alphabetical order of topics

@zaziemo
Copy link
Member Author

zaziemo commented Apr 9, 2015

Hey @pohameera, that's great! Are you planning to apply for Rails Girls Summer of Code: rails-girls-summer-of-code/projects#14?

@pohameera
Copy link

Yes, we are applying for Rails Summer of Code. We are interested in doing
your project for RSoC. So it would be great if you mentor us. We would like
to know how we can contribute to the project. We actually thought that we
can start off with localisation of contents but we need your help and
guidance on what exactly we need to do, Awaiting for your suggestions,

Thanks,
Ameera

On Fri, Apr 10, 2015 at 2:06 AM, zaziemo notifications@github.com wrote:

Hey @pohameera https://github.com/pohameera, that's great! Are you
planning to apply for Rails Girls Summer of Code:
rails-girls-summer-of-code/projects#14
rails-girls-summer-of-code/projects#14?


Reply to this email directly or view it on GitHub
#216 (comment)
.

@zaziemo
Copy link
Member Author

zaziemo commented Apr 10, 2015

Hey @pohameera, wonderful!
Concerning the content localization: that's really a big and important issue. That was part of the project of last summer of code's team and they finally decided to focus on other things (see their blog post that is linked in the issue). It would be great to think it over again: currently we have no clear concept of handling variable content that is provided by the speakers themselves in multiple languages - especially the tags. Right now we have more than 3000 tags in different languages. Some things are in progress right now that help in other segments of the problem: advanced search and new speaker profile editing. How we will proceed with content localization is also dependent on what we can cover with these improvements.
Long story short: this is a highly interesting issue, but right now I can't specify what should be done exactly. But I would highly appreciated working and discussing a concept with you.

@robinboening
Copy link

If you use labels on the issues they might be found more easy. One thing we do to collect issues for http://rubyissues.ongoodbits.com is to filter all ruby related issues from GitHub by labels.

So, if you have a label documentation, beginner, feature, bug we can find them this way :)

@zaziemo
Copy link
Member Author

zaziemo commented Aug 27, 2015

@robinboening yeah, thanks! That's a good idea. We'll implement that in the next days :)

@zaziemo zaziemo removed the Prio 1 label Sep 23, 2015
@nerdinand
Copy link
Contributor

I've got a real itch in my fingers when I see some of the code, but I'm not sure whether it's wise to do a huge pull request...

@tyranja
Copy link
Member

tyranja commented Sep 29, 2015

How about working step by step? Just pick one topic at a time, make a small pull request and write your motivation behind it as comment. That way its easier for us to comprehend. 👍 Its great that you found the time to look trough the code. 😃

@zaziemo
Copy link
Member Author

zaziemo commented Sep 30, 2015

@nerdinand hehe ;) but what @tyranja says.

@ramyaravindranath
Copy link

Hi @tyranja I and my team mate are planning to work on Speakerinnen this year at RSOC. The concept looks very interesting and it also involves rails. As we both are very keen on learning rails, this would a great opportunity for us. Could you please let me know what is the eligibility criteria for applying? I would also like to get in touch with people who had worked last year to know more about their learning experience and also about the application process? Could you please help me on this?

@cesc1989
Copy link
Contributor

Hello. Just wanted to know whether there's an active maintainer for this project. I'd like to tackle some issues and update some docs as well.

@tyranja
Copy link
Member

tyranja commented Sep 30, 2016

Hello @cesc1989, Yes, we ( @zaziemo and me ) are the maintainers of that project. What exactly do you want to work on? And how did you find that project?

@cesc1989
Copy link
Contributor

It is good to know, @tyranja :)

I found this project following the beginner label from a search in the github search bar.

Regarding the issues, ATM I'd like to work in:

Speakerinnen Project Management Board automation moved this from To do to Done Oct 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests