Skip to content

Latest commit

 

History

History
241 lines (185 loc) · 17.7 KB

README.md

File metadata and controls

241 lines (185 loc) · 17.7 KB

devs

All Contributors

style: very good analysis

Setup

Currently, this DEVS project is using the master channel of the Flutter SDK.

TODO: Migrate to beta

Clone the project

git clone https://github.com/flutterph/devs/

Download dependencies

Open the project in an IDE or text-editor, then run the ff:

cd devs
flutter packages get

Run the project for web

flutter run -d web

Run the project for mobile

TODO: Add responsiveness for mobile

Contributing

#30DaysOfFlutter Activies

1. Add Developer Details (1 Point)

  1. Create an new ticket here

Title: Add details

Body (Optional): More details about you

  1. Fork this repository
  2. Clone (or download) the fork repository on your machine
  3. Create a new branch
git checkout -b <ticket-number>/your-name
  1. Locate and open the file assets/data/devs.json
  2. Add your details
[
  {
    "name": "Joshua",
    "roles": ["Software Engineer", "Flutter and Dart GDE"],
    "about": "Lorem ipsum",
    "username: "joshuamdeguzman",
    "socials": {
          "twitter": "",
          "facebook": "",
          "linkedin": ""
      }
  },
  {
    "name": "Jan Salvador S. Sebastian",
    "roles": ["Software Engineer", "Flutter"],
    "about": "Lorem ipsum",
    "username: "JanSalvador1445",
    "socials": {
          "twitter": "",
          "facebook": "",
          "linkedin": ""
      }
  },
  ...
  // Add here
]
  1. Commit changes

Add your name

git commit -m "Add <your-name> details"
  1. Push the changes
git push origin -u <ticket-number>/your-name
  1. On Github, open the fork repository

  2. Locate the branch

  3. Create a pull request

  4. Submit pull request for review

General Contributing

1. Feature Development

  1. Comment on the ticket you would like to work on
  2. Outline your proposed solution
  3. Get feedback from maintainers
  4. Work on the feature
  5. Create a pull request
  6. Submit pull request for review

2. Fixing bugs

  1. Comment on the ticket you would like to work on
  2. Outline your proposed solution
  3. Get feedback from maintainers
  4. Work on the bug fix
  5. Create a pull request
  6. Submit pull request for review

3. Filling bugs

4. Feature requests

  1. Create a new issue using the 'Feature Request 💡' template
  2. Fill in the requested information and feel free to add headers if there's anything you think we missed!
  3. Submit the new issue

For questions or suggestions, either create a ticket or send us an email at [email protected].

More on Contributing.

Commands

Before creating Pull Request

Format files

flutter format --set-exit-if-changed .

Analyze files

flutter analyze .

Contributors ✨

Thanks goes to these wonderful people (emoji key):


Joshua de Guzman

💻 🖋 🔣 🧑‍🏫 🐛

digitaljoni

🖋 🧑‍🏫

Vince Ramces Oliveros

💻 🖋 🐛

Medwin Correo

🖋

Karlo Barcelona

🖋

Barrientos Mark Zamie

🖋

Haji Fernandez

🖋

Anike Nicole Dorgu

🖋 📖

Celesica

🖋

Kean Allen Imam

🖋

Muslimin Ontong

🖋

Roneal Denila

🖋

Felix Jerome Dela Fuente

🖋

charlzmagno

🖋

Radhika

🖋 📖

Jan Salvador Sebastian

🖋 🧑‍🏫 💻 🐛

KarlJan Reginaldo

🖋

Eastly1997

🖋

Lester Araña

🖋

Lorns15

🖋 💻 🎨

janfrncs

🖋

Kim Arthur Lorenzo

🖋

mgcarpizo

🖋

Zaldy Pagaduan Jr.

🖋

Sherwyne

🖋

EruelUrsua

🖋

Ca

🖋

Jeofferson Dela Peña

🖋

Rian

🖋

RaineHolgado

🖋

Zen Rabanes

🖋

John Patrick Prieto

🖋

Kevin Tuazon

🖋

K

🖋

Bern Lester Givertas

🖋

Royce

🖋

lidaniel5

🖋

Venus Lumanglas

🖋

Jan Dranreb Balangue

🖋

Portia Bumanlag

🖋

Vincent

🖋

Jose Jaime Bisuña

🖋 🎨 💻

Darryl Llanura

🖋

Ipancho

🖋

Kathorsiii

🖋

Jed Aureus Gonzales

🖋

Oliver Rhyme Guibone Añasco

🖋

Mher Tan

🖋

Ritzi April Lontoc

🖋

This project follows the all-contributors specification. Contributions of any kind welcome!