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

Add team profiles #69

Open
sschiessl-bcp opened this issue May 3, 2019 · 36 comments
Open

Add team profiles #69

sschiessl-bcp opened this issue May 3, 2019 · 36 comments
Assignees
Labels
content Content Management enhancement New feature or request good first issue Good for newcomers P1 High Priority issue

Comments

@sschiessl-bcp
Copy link

sschiessl-bcp commented May 3, 2019

Add a Team website that explains that there is no team, but that there are workers and the teams behind those workers could be considered as a part of the team.

Then list the people involved like known on other team websites. This could be only listing the main people involved and show what teams they are part of, or as complete as desired. People could opt-in / opt-out and so on

@dls-cipher dls-cipher added content Content Management enhancement New feature or request good first issue Good for newcomers P1 High Priority issue labels May 3, 2019
@dls-cipher
Copy link
Contributor

dls-cipher commented May 3, 2019

@rsswlkr - Collect the data from the following teams:

  • BitShares core team
  • BitShares UI team
  • BitShares Beet team
  • BitShares Community UI team
  • BitShares.org team
  • BitShares Marketing team
  • BitShares Legal team

Data = Names (nicknames/handles where names are not applicable), profile photos(avatars for people like @abitmore), positions, short description (if available).

We can move on from there.

@sschiessl-bcp
Copy link
Author

sschiessl-bcp commented May 3, 2019

Before we collect any data we should discuss if we want that, and if we do, work out the exact text that goes on the team page (to not insinuate any partnerships or affiliations where there are none).

If we then are happy we can collect data.

Thougts @xeroc @ryanRfox ?

@rsswlkr
Copy link
Contributor

rsswlkr commented May 3, 2019

I can work on collecting the information in the background, template for the page, and placeholder text - will take feedback/input on it from here also.

Acknowledged @sschiessl-bcp on waiting for thoughts /input from others.

@ryanRfox
Copy link

ryanRfox commented May 3, 2019

Please add to the Teams list:

  • DEXbot Team
  • Infrastructure Team (although we may have multiple teams funded, please collapse into single heading)

@sschiessl-bcp
Copy link
Author

sschiessl-bcp commented May 3, 2019

Please add to the Teams list:

  • DEXbot Team
  • Infrastructure Team

And mobile team and Rossul/G, HackTheDex

@sschiessl-bcp
Copy link
Author

(although we may have multiple teams funded, please collapse into single heading)

The team overview should be people driven IMO, bot project driven (there could be a project site too). People site lists people and within a person you can list what projects they are involved.

@abitmore
Copy link
Member

abitmore commented May 4, 2019

Also tagging @syalon for mobile app team.

@syalon
Copy link
Member

syalon commented May 5, 2019

What data is needed?

@bitshares bitshares deleted a comment from rsswlkr May 5, 2019
@dls-cipher
Copy link
Contributor

What data is needed?

List of team members, their github handles, linkedin profiles (if applicable), real names and profile pics.

@dls-cipher
Copy link
Contributor

dls-cipher commented May 5, 2019

(although we may have multiple teams funded, please collapse into single heading)

The team overview should be people driven IMO, bot project driven (there could be a project site too). People site lists people and within a person you can list what projects they are involved.

Currently discussion is Team page on bitshares.org and please don't expand it until we have that one sorted out :) Baby steps when it comes to structure, and how I see - its a first timer in BitShares :)

P.S. I agree on project sites - DEXBot is nice. HackTheDex needs a bit of polishing though :) Some good ninja form instead of contact would be making submissions a lot easier to be

  • created/sent
  • reviewed
  • notified on them.

@rsswlkr
Copy link
Contributor

rsswlkr commented May 23, 2019

Please see draft of this team page content attached.

BitShares-teams.docx

@pmconrad
Copy link

Please see draft of this team page content attached.

Thanks! FTR, I'm not writing a book. I have written an introduction on Bitcoin back in 2013. :-)

Hint: T. Sugimoto is a she.

@ryanRfox
Copy link

ryanRfox commented May 23, 2019

Under Core Team

  • Please add:

  • Please change Dr. Snaborn's role to "Core Developer"

  • Please change T. Sugimoto's role to "Lead Documentation Specialist, QA/Tester"

  • Please change Ryan R. Fox's role to "Development Coordinator"

@syalon
Copy link
Member

syalon commented May 25, 2019

@rsswlkr please add mobile tam.

BitShares Mobile App Team

Project link: https://github.com/bitshares/bitshares-mobile-app

Main team members

Syalon Flauspid

Core Developer

GitHub: https://github.com/syalon

Syalon is a natural programmer. Have rich passion and focus on what he does. He has accumulated rich experience in the field of Internet products and Game development for more than ten years. He began researching the blockchain from contact with Bitcoin in 2012, and in the past year he has been researching bitshares and creating the btspp team. participate in the governance of the community.

Yang Ming

Designer / Tester

Yangming comes from the traditional financial and service industries and has a keen insight into user experience and detail needs. In the past two years, he has been working on the analysis of bitshares and create the btspp team with syalon. participate in the governance of the community.

Qing Feng

Android Developer

Qingfeng has an early interest in blockchain technology and has a strong interest in blockchain technology. He began researching BTS in 2017 and is currently responsible for the development of the Android portion of the bitshares mobile app. In addition, he is good at the ruby programming language, the Ruby On Rails web framework. Has extensive front-end development experience (html, css, javascript)

@sschiessl-bcp
Copy link
Author

Could we make this a Google Doc and allow suggesting @rsswlkr?

Either way will give feedback next week.

@dls-cipher
Copy link
Contributor

@rsswlkr please add mobile tam.

BitShares Mobile App Team

Project link: https://github.com/bitshares/bitshares-mobile-app

Main team members

Syalon Flauspid

Core Developer

GitHub: https://github.com/syalon

Syalon is a natural programmer. Have rich passion and focus on what he does. He has accumulated rich experience in the field of Internet products and Game development for more than ten years. He began researching the blockchain from contact with Bitcoin in 2012, and in the past year he has been researching bitshares and creating the btspp team. participate in the governance of the community.

Yang Ming

Designer / Tester

Yangming comes from the traditional financial and service industries and has a keen insight into user experience and detail needs. In the past two years, he has been working on the analysis of bitshares and create the btspp team with syalon. participate in the governance of the community.

Qing Feng

Android Developer

Qingfeng has an early interest in blockchain technology and has a strong interest in blockchain technology. He began researching BTS in 2017 and is currently responsible for the development of the Android portion of the bitshares mobile app. In addition, he is good at the ruby programming language, the Ruby On Rails web framework. Has extensive front-end development experience (html, css, javascript)

Can you please post here Chinese translation for this with same formatting (paragraphs, spaces, etc) ? Multi-language on website is getting ready, so just to not do it 2 times, if not have to.

Thanks!

@rsswlkr
Copy link
Contributor

rsswlkr commented May 26, 2019

Thanks @ryanRfox , do you have any short bio paragraph for Nathan also?

@rsswlkr
Copy link
Contributor

rsswlkr commented May 26, 2019

@rsswlkr please add mobile tam.

BitShares Mobile App Team

Project link: https://github.com/bitshares/bitshares-mobile-app

Main team members

Syalon Flauspid

Core Developer

GitHub: https://github.com/syalon
Syalon is a natural programmer. Have rich passion and focus on what he does. He has accumulated rich experience in the field of Internet products and Game development for more than ten years. He began researching the blockchain from contact with Bitcoin in 2012, and in the past year he has been researching bitshares and creating the btspp team. participate in the governance of the community.

Yang Ming

Designer / Tester

Yangming comes from the traditional financial and service industries and has a keen insight into user experience and detail needs. In the past two years, he has been working on the analysis of bitshares and create the btspp team with syalon. participate in the governance of the community.

Qing Feng

Android Developer

Qingfeng has an early interest in blockchain technology and has a strong interest in blockchain technology. He began researching BTS in 2017 and is currently responsible for the development of the Android portion of the bitshares mobile app. In addition, he is good at the ruby programming language, the Ruby On Rails web framework. Has extensive front-end development experience (html, css, javascript)

Can you please post here Chinese translation for this with same formatting (paragraphs, spaces, etc) ? Multi-language on website is getting ready, so just to not do it 2 times, if not have to.

Thanks!

Added, note that all bios have been abridged to fit approx 3 lines or < 260 chars. Would only need translation of final (short) version.

@rsswlkr
Copy link
Contributor

rsswlkr commented May 26, 2019

Could we make this a Google Doc and allow suggesting @rsswlkr?

Either way will give feedback next week.

Here we are @sschiessl-bcp - this version with edits as per feedback in comments above.

https://docs.google.com/document/d/17vU3x-yTZFM20KGLH0nrOcoS8M5_azUw4FGNXQO57oE/edit?usp=sharing

(P.S. Blame Google Docs for the pretty link)

@PermieBTS
Copy link

PermieBTS commented May 26, 2019

To the DEXBot team bio can we also add the rest of the team?

Codaone - Build Maintainers - Have been part of the project since day one. https://www.codaone.fi/en/company/

BitProfessor - Quality Assurance Engineer -
I've been involved in Bitshares since 2016. I became a big fan. I am one of the participants in the high value proxy cn-vote. I developed an automatic mortgage bot, a triangular arbitrage bot using python, pybitshares and uptick. I am also a believer in Austrian economics and a free economy. I am the CIO of a Chinese company. I used to do ERP dev work. Way back I studied computer science and have an MBA.

Jacko - Charting and Visualisation Developer - https://github.com/Jackodb
Developer and long term Bitshares and DEXBot community member.

JR Pasch - Charting and Visualisation Developer - https://github.com/Jrizzly
I produced some personal graphing tools for Bitshares and posted a few screenshots in the DEXBot telegram and got a good response, which lead me to joining the DEXBot team.

Dominic - Dedicated Windows Developer
I jumped on the crypto hype in mid 2017 and was overwhelmed by the promising technology. I examined smart contracts on EOS and Ethereum after which I created a block explorer with some temporal progression to provide analysis for user account balances.
I discovered DEXBot from a recommendation in an EOS chatroom.
My day job is a software engineer with a focus on web applications.
3 years Windows desktop application experience.

The Cabinet - Worker Proposal Management and Multisig Security
The Cabinet was formed in early 2018 to unite 6 Bitshares community members in a team focussed on efficient allocation of Reserve Fund resources to invest in Bitshares. Our debut project is DEXBot.
The Cabinet operate a 3 of 6 multisignature Bitshares account to hold all WP funding.

Cabinet Members:
Permie - DEXBot Project Manager

Cryptick1 - (BIO already in the google doc - please paste it here)

Cryptokong - I joined Bitshares in 2017 where I discovered the great potential of decentralised markets and permissionless trading. I worked with the Cabinet to help build the tools for anyone to lay the foundations for a healthy market. I'm an electrical engineer by trade and have always had an interest in finance. My goal is to create healthy and thriving decentralised marketplaces that are open to all.

Marko Paasila - DEXBot PM 2018

Don_Gabriel - PR and Website Management

Kimchiking - Kevin Messerley - PR, Bitshares Tweeter, Bitshares Proxy

@syalon
Copy link
Member

syalon commented May 27, 2019

@dls-cipher Chinese version added

BitShares Mobile App 团队

项目仓库地址: https://github.com/bitshares/bitshares-mobile-app

主要团队成员

小夏

核心开发者

GitHub: https://github.com/syalon

小夏是天生的程序员。对所做的事情拥有极高的热情和专注度。在十多年的互联网产品和游戏开发中积累了丰富的经验。从2012年接触比特币开始对区块链进行研究。在2017年开始接触比特股并创立了btspp团队。一直努力参与到社区的开发和治理中。

洋明

设计师 / 测试

洋明来自传统金融及服务行业,对用户体验和细节需求有着敏锐的洞察能力。在过去的两年他一直致力于比特股的分析并和小夏他们一起成立的btspp团队,参与到社区的治理当中。

清风

安卓工程师

清风较早开始接触区块链,对区块链有浓厚的兴趣,2017年开始研究BTS。目前主要负责Bitshares Mobile App安卓部分的开发。除此之外擅长ruby编程语言,rails框架等。具有丰富的前端开发经验。

@dls-cipher
Copy link
Contributor

dls-cipher commented May 27, 2019

To the DEXBot team bio can we also add the rest of the team?

Codaone - Build Maintainers - Have been part of the project since day one. https://www.codaone.fi/en/company/

BitProfessor - Quality Assurance Engineer -
I've been involved in Bitshares since 2016. I became a big fan. I am one of the participants in the high value proxy cn-vote. I developed an automatic mortgage bot, a triangular arbitrage bot using python, pybitshares and uptick. I am also a believer in Austrian economics and a free economy. I am the CIO of a Chinese company. I used to do ERP dev work. Way back I studied computer science and have an MBA.

Jacko - Charting and Visualisation Developer - https://github.com/Jackodb
Developer and long term Bitshares and DEXBot community member.

JR Pasch - Charting and Visualisation Developer - https://github.com/Jrizzly
I produced some personal graphing tools for Bitshares and posted a few screenshots in the DEXBot telegram and got a good response, which lead me to joining the DEXBot team.

Dominic - Dedicated Windows Developer
I jumped on the crypto hype in mid 2017 and was overwhelmed by the promising technology. I examined smart contracts on EOS and Ethereum after which I created a block explorer with some temporal progression to provide analysis for user account balances.
I discovered DEXBot from a recommendation in an EOS chatroom.
My day job is a software engineer with a focus on web applications.
3 years Windows desktop application experience.

The Cabinet - Worker Proposal Management and Multisig Security
The Cabinet was formed in early 2018 to unite 6 Bitshares community members in a team focussed on efficient allocation of Reserve Fund resources to invest in Bitshares. Our debut project is DEXBot.
The Cabinet operate a 3 of 6 multisignature Bitshares account to hold all WP funding.

Cabinet Members:
Permie - DEXBot Project Manager

Cryptick1 - (BIO already in the google doc - please paste it here)

Cryptokong - I joined Bitshares in 2017 where I discovered the great potential of decentralised markets and permissionless trading. I worked with the Cabinet to help build the tools for anyone to lay the foundations for a healthy market. I'm an electrical engineer by trade and have always had an interest in finance. My goal is to create healthy and thriving decentralised marketplaces that are open to all.

Marko Paasila - DEXBot PM 2018

Don_Gabriel - PR and Website Management

Kimchiking - Kevin Messerley - PR, Bitshares Tweeter, Bitshares Proxy

@PermieBTS Have you checked:

a) 3 line description up to 250 characters in 3rd person
b) only active worker members
c) check last upload/google docs ->> whats up with current content that was sent to @rsswlkr - redo ?

Chee®s

@sschiessl-bcp
Copy link
Author

In general I would only list members / entities that are specifically mentioned in the worker and/or homepage of the project, not every contributor.

@sschiessl-bcp
Copy link
Author

Could we make this a Google Doc and allow suggesting @rsswlkr?
Either way will give feedback next week.

Here we are @sschiessl-bcp - this version with edits as per feedback in comments above.

https://docs.google.com/document/d/17vU3x-yTZFM20KGLH0nrOcoS8M5_azUw4FGNXQO57oE/edit?usp=sharing

(P.S. Blame Google Docs for the pretty link)

I did want the google doc to be able to fill in suggestions :P

@PermieBTS
Copy link

PermieBTS commented May 27, 2019

In general I would only list members / entities that are specifically mentioned in the worker and/or homepage of the project, not every contributor.

Ok if this is the procedure then the team bio should additionally include the Cabinet and Codaone by name.
https://www.dexbot.info/2018/12/12/cabinet-multisig-dexbot-wp2/

The Cabinet - Worker Proposal Management and Multisig Security
The Cabinet was formed in early 2018 to unite 6 Bitshares community members in a team focussed on efficient allocation of Reserve Fund resources to invest in Bitshares. The Cabinet's debut project is DEXBot.
The Cabinet operate a 3 of 6 multisignature Bitshares account to hold all WP funding.

Marko Paasila - Marko found BitShares in 2014. Instead of just talking he began encouraging others to join and get something done. Marko managed the DEXBot project through it's first year (2018). Marko enjoys system dynamics, econonmics, maths and programming.

FYI DEXBot WP3 is due for release and voting soon. In the WP the full DEXBot teamed are named and their roles explained. Once WP3 is live can the whole team be added to this team website?

@dls-cipher

@dls-cipher
Copy link
Contributor

dls-cipher commented Jun 4, 2019

Please review, desktop mockup/design is done with ALL ELEMENTS VISIBLE (including hidden ones - no prettifying).

Since it's really long and extensive page, basic idea is to navigate from the top through teams using anchor links (scroll to the team - ok for responsive or even open popup for the team - problematic for responsive)

Team

Disclaimer: Ignore double entries, wrong worker info - Designer is new to the ecosystem, content isn't really correct 100% (but amount is real).

Chee®s

@PermieBTS
Copy link

Hi, looks good

At the very top of the page introducing all of the Teams by name: would it be possible to change the DEXBot team name from "DEXBot WP2" to just "DEXBot"?
WP2 expires at the end of this month and then WP3 is due to start

All DEXBot WPs will be focussing on the developement of DEXBot so I think that the "WP2" text is not needed

Thanks

@dls-cipher
Copy link
Contributor

@PermieBTS - no issues, as disclaimer says, content is not final/correct :) I agree that your team should be DEXBot Team only, without part of the worker you are doing.

Everybody else, please some comments/input so we can move on with design or start deployment for real page.

Chee®s

@rsswlkr
Copy link
Contributor

rsswlkr commented Jun 4, 2019

Updated to reflect more of above feedback. As mentioned, not final content yet. Adding short opening paragraph, explaining the 'teams' are individuals from workers, not from BitShares itself. I've started draft on that statement, input welcome.

Still missing quite a few GitHub or LinkedIn profiles from people, also some bios and all should be reviewed or given some more input/interesting facts about the people being presented. Please check your teams bios ...

teams content - google docs

@dls-cipher dls-cipher added this to the June 1/2 Sprint milestone Jun 4, 2019
@syalon
Copy link
Member

syalon commented Jun 4, 2019

@dls-cipher missed the bitshares mobile team?

@dls-cipher
Copy link
Contributor

dls-cipher commented Jun 4, 2019

@syalon :

@dls-cipher missed the bitshares mobile team?

I believe not, how I can see in the google docs from @rsswlkr above your comment - you are in the list.

If you were referring to mockup design - it was started before any content updates and it's far from final :)

Chee®s

@sschiessl-bcp
Copy link
Author

Can the link selector be a filter and not a scroll-link? With the amount of projects we have I would find that more appropriate

@dls-cipher
Copy link
Contributor

image

image

Re-organized design in order to sort out space that 30+ members are using with their full descriptions... And definitely filter through workers is non-sense, since some members are repeating/and/or involved between.

Hope to see some positive feedback and deploy this.

@rsswlkr please update all team members in document and replace current DEXBot team with new DEXBot WP3 team.

Chee®s

@sschiessl-bcp
Copy link
Author

You can combine the view into "grouped by worker" or grouped by contributor". If grouped by contributor you get something similar to this and if grouped by worker you get something similar to this.

The raw data needed to fill this is:

  • details on workers (description, list of members)
  • details on contributors (description, list of workers)

In such a view it would make sense to be able to filter by worker name and contributor name

@rsswlkr
Copy link
Contributor

rsswlkr commented Jun 18, 2019

@rsswlkr please update all team members in document and replace current DEXBot team with new DEXBot WP3 team.

I am still actively working on the document which can be accessed anytime. I expect to be done with it by today. All content is being reorganized into workers (projects) and contributors (people). Sorted alphabetically by first name. It's too much manual process so I think I will put this into a spreadsheet next.

You can access the current doc here

@rsswlkr
Copy link
Contributor

rsswlkr commented Jun 18, 2019

Further to above comment, I have since completed tidy up of all the data. Now is a state ready to deploy, whereby it becomes a living document.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Content Management enhancement New feature or request good first issue Good for newcomers P1 High Priority issue
Projects
None yet
Development

No branches or pull requests

9 participants