Weekly community Check-In #26 (Bash Aliases)

[sashadev-sky]

Hi everybody 😃 !

We all at Public Lab 🎈 - learn, grow, work, brainstorm ideas, contribute together so why not share about our weekly goals and the awesome work we have done at Public Lab with each other, so we can support and collaborate with each other better. We have a Community Check-In each week, where every community member can share something about their work from the past week and about their current week's goal 🎯 . You are also welcome to share fun-fact 😄 , new ideas 💡 , your learning goals ☑️ .

We believe in collaborative efforts to support our community. We are running a learning platform which helps a newcomer to become master of tomorrow. 💯

If you're new here, welcome, and please comment a Hello below, we would love to work with you. If you're looking for new issues, please try some of our first-timers-only issues.

We're SO EXCITED to have your help!

Is there anything, you would like to share with us from past week's work? What is your plan for this week?

If you have not planned yet, just leave a Hello! 👋 so that we know that you are in sync with us 🔃 and doing well!

The coming weeks will be full of code 💻 , tasks 🗒️, fun 🎉 and excitement 😃!!

As always, if you're waiting for a review, or if you're stuck, please request help here OR leave a comment with @publiclab/mentors @publiclab/reviewers for some input. 🙌

Gitter

Gitter is an active chatroom in our community and we'll be sending weekly reminders about check-ins there. Be sure to sign up there for these updates or just to join the conversation. You can also join us through http://publiclab.org/chat 💬.

This Week's Theme:

Bash Aliases: Bash aliases provide my greatest productivity boost. They also have become a reflection for myself for how my workflow has increased in sophistication over time and new knowledge I have gained.

This week, tell us an interesting bash alias you use. If you don't use any or have a good one to share, try looking one up and sharing that! Everyone is encouraged to discover and start using a new alias this week either through online research or from someone else's post here.

For those not familiar with them:

• open your bash profile (found at ~/.bash_profile) in your code editor
• add an alias and save. Here is a simple ex. that demonstrates the correct syntax: alias be="bundle exec"
• reload your current terminal session with source ~/.bash_profile
• the alias will now be available

You can find our list of previous check-ins here

Note to Summer of Code interns:

Hi, we request all the SoC students to include the below-mentioned points in their check-in comment:

• FTOs created in the previous week
• Progress for your project
• Upcoming week's goals
• PR reviewed by you in the previous week
• Work completed last week.
• What things you did collaboratively last week? This is really important we want team spirit.
  It is like a weekly scrum. Be flexible.
• Feel free to tell us about your absence too, if you're taking a break.
• Issue/PR you're struggling with (if any)

With FTOs and PR reviews, we are seeking to develop a much more friendly and collaborative platform. We want you all will involve people in your project. You all will develop skills like leadership along the way.

Thank you!

[sashadev-sky]

@milaaraujo @kevinzluo @Rishabh570 @sashadev-sky @shubhscoder @sidntrivedi012 @SidharthBansal @cesswairimu @stefannibrasil @ViditChitkara @tech4GT @mridulnagpal @IshaGupta18 @coderjolly @namangupta01 @sagarpreet-chadha @Souravirus @MayankKashyap @siaw23 @ryzokuken @icarito @steviepubliclab, @ebarry, @jywarren, @sagarpreet-chadha, @JonathanXu1, @uzorjchibuzor, @eli6, @rexagod, @divyabaid16, @dinaelhanan, @oorjitchowdhary @publiclab/mentors @publiclab/image-sequencer-guides @publiclab/leaflet-environmental-layers-guides @Paarmita @publiclab/reviewers @Divy123 @Mridul97 @avsingh999 @romanrodriguez @Dhiraj240 @codeIriss @IgorWilbert @pdurbin @harshkhandeparkar @aashna27

[sashadev-sky]

@mohitRJranjan @milaaraujo @kevinzluo @Rishabh570 @sashadev-sky @shubhscoder @sidntrivedi012 @SidharthBansal @cesswairimu @stefannibrasil @ViditChitkara @tech4GT @mridulnagpal @IshaGupta18 @coderjolly @namangupta01 @sagarpreet-chadha @Souravirus @MayankKashyap @siaw23 @ryzokuken @icarito @steviepubliclab, @ebarry, @jywarren, @sagarpreet-chadha, @JonathanXu1, @uzorjchibuzor, @eli6, @rexagod, @divyabaid16, @dinaelhanan, @oorjitchowdhary, @wanzulfikri, @mohitRJranjan @publiclab/mentors @publiclab/image-sequencer-guides @publiclab/leaflet-environmental-layers-guides @Paarmita @publiclab/reviewers @Divy123 @bhavayAnand9 @Mridul97 @avsingh999 @romanrodriguez @Dhiraj240 @codeIriss @rishabhc32 @chirag-singhal @IgorWilbert @vrk99 @pdurbin @harshkhandeparkar @niravasher @Marieram @publiclab/reviewers @publiclab/is-reviewers @publiclab/community-reps @divyabaid16

[sashadev-sky]

@publiclab/community-reps @subhahu123 @An0u @Jaya738 @mgroovyank @shreyateeza @TANGL3SIT3S @nazeem1988 @karunagoyalk @Nirvikalpa108 @cassianoblonski @EngrEric @Anjalizi @GettyOrawo @coderbeetle @corbettbw @govindjeevan @gautamig54 @daddyjab @emestabillo @letnewKid @srujana121 @jazdao @chinwendusilvia @aggarwal19 @Jenniline @madelinejones @helenatxu @richa031 @FabSar @kuja24 @megha070 @Aarabhi2017 @Manvi07 @siddhishree @Julius26 @VinneyJ @sonali9696 @rarrunategu1 @coreytegeler @labseven @milomacphail @CleverFool77 @ananyaarun @ananya @publiclab-mimi @shubhi2000

[sashadev-sky]

@Priyak5 @techchic @ananya @hc-barker @edwd42 @PritiShaw @themonster2015 @supriya-kotturu @AnthoniaOkafor @scheleon @mahmodHammad @santushk @jillpena @stoic-plus @starkblaze01 @asquare14 @vaarigupta @alonpeer @madeofhuman @ibnjunaid @aashna27 @harshithpabbati @mmmelissa @rarrunategu1 @UNnamed66 @GauravJ3 @Greg-Tarr @Sanscripter @hodbadger @alaxalves @becomingajunior @monsij @vrk99 @pdurbin @harshkhandeparkar @aashna27 @harshithpabbati @CleverFool77 @niravasher @gautamig54 @jesus-montano @michelelong @cryptoclidus

[sashadev-sky]

note @alaxalves will be opening next weeks!

[asquare14]

@sashadev-sky Great topic for the cheeckin ! Bash is highly underrated I feel and an amazing tool :)
One bash alias I use is alias ports=netstat -t
Hoping everyone has a great week ahead !

[kaustubh-nair]

HI all! And nice topic @sashadev-sky ! 😃
I use a lot of aliases while working, mostly for rails and git
Here are some of them

alias c="clear"
alias lg="ls -a | grep"
alias rdm="rails db:migrate"
alias rg="rails generate"
alias rr="rails routes"
alias rdc='rails db:create'
alias rc='rails console'
alias rds='rails db:seed'

I also wrote some really cool functions for git, which I use a lot.
$1 and $2 denote the first and second arguments in shell script
So if you type 'gp beta master', it will push to 'beta' remote and 'master' branch

gc(){
  git add .
  git commit -m "$1"
}
gp(){
  git push $1 $2
}
gpo(){
  git push origin $1
}
gpu(){
  git push upstream $1
}
# And similar for pulling

I also highly recommend using zsh instead of bash. It's a lot faster, and has amazing auto completion. Once you switch you will never look back 😄

Summer of code update for Mapknitter Rails upgrade

This week I've been helping fix the asset issues that have arisen due to the yarn switch. We'll hopefully fix all of these this week and get Rails 4 deployed to the main site!
We were stuck on setting up the database for Rails 5 last week, but the errors turned out to be because to some manual overrides that were done previously for the mysql_adapter ( thanks @sashadev-sky ).
Since then, we've fixed all the tests and got the build passing for Rails 5 publiclab/mapknitter#685 🎉 🎉
There's still a lot of deprecation warnings to fix, which we'll address after finishing setting up Rails 4!
Thanks!

[harshkhandeparkar]

Hi, I don't set any bash aliases as such but I have some scripts which boost the productivity a lot.

• https://github.com/HarshKhandeparkar/bashinthebin
• https://github.com/HarshKhandeparkar/gitshot (under devel)
• https://github.com/harshithpabbati/Update-is (for deploying image sequencer beta)

[alaxalves]

Hey guys, to be honest I am not a big fan of setting aliases on my bash, because I like remembering the entire command 😄 😄 😄. But I have set some useful functions on my bash to integrate it better with git commands. Here they go:

function git_branch_name() {
        git branch 2>/dev/null | grep -e '^*' | sed -E 's/^\* (.+)$/(\1)/'
}

function show_colored_git_branch_in_prompt() {
        PS1="\[\033[01;32m\]\u@\h:\[\033[01;34m\]\w\[\033[31m\]\$(git_branch_name)\[\033[m\]$ "
}

show_colored_git_branch_in_prompt

With those two functions you can quickly identify if it is a git versioned repo, and easily know where you at haha, it will prompt out something like this:

Now about my GSoC project progress, here we go:
Mostly of my last week work can be found at publiclab/mapknitter#685

Progress

Currently me and @kaustubh-nair are pretty in advance with our work, thanks to @IgorWilbert's suggestion I have "skipped" a version and went straight ahead to Rails 5.2.3 version(latest stable rails).

Upcoming goals

I plan to fix the deprecation warnings that are still left, change folder names to the newest rails conventions, investigate the simplecov integration and fix some assets related bugs along with @kaustubh-nair. Also I'd like to start testing with Rails 6.0.0-rc1 version, but only after Rails 5.2.3 gets merged to development branch.

Work completed last week

• Removed deprecated method invokations, such as atr_acessible.
• Locked every version of our gems, to latest possible.
• Fixed broken CI pipelines(Unit tests and docker building).
• Fixed the MySQL adapter integration, (had a huge help of @sashadev-sky).
• Started using strong_params.
• Started making model associations "weak".
• Included abstracted classes for ApplicationMailer and ApplicationRecord.
• Using required_relative in favor of plain require.

** What things I did collaboratively last week?**

I have been working mostly with @kaustubh-nair and @sashadev-sky only. Me and Kaustubh have been organizing our work pretty nicely, there's never been a mismatch or conflict.
I am also digging this issue -> publiclab/mapknitter#725 with Kaustubh.

[grvsachdeva]

Hi everyone,

Nice theme @sashadev-sky!

I don't use aliases. Because I can't remember them and using complete command help me picture the effect better.

Plots2:

I am going through plots2 old issues/PRs, pushing some to completion, and closing some of them.

Goals:

1. Notification system PR review
2. Plots2 issue template setup
3. Image management project update

have a great week 💯

[sashadev-sky]

Just implemented @alaxalves script! 🚀

I use an alias for grabbing the name of the branch i'm on:

alias me='git rev-parse --abbrev-ref HEAD'

Which allows me to do $ git push origin $me to quickly push up my work from a branch

This week my goal is to complete the progress update UI for the exporting system!

[jywarren]

Hi all! It was great talking to folks on the Code Open Call today (https://pad.publiclab.org/p/opencall) and we took lots of notes.

@IshaGupta18 I tried making a diagram of your app flow - take a look and try making your own!

This is a good exercise for everyone! You can try starting on page 2 of thsi doc, but please copy the slide so you don't mess up others' work: https://docs.google.com/presentation/d/1aquQKyih8vvtD7U-AI0NlbAcgT-BVu9G8hloYg-c-QI/edit#slide=id.g1b2a1e1ee8_0_82

I also wrote a good bit about managing variable scope and overwriting values in @ananyaarun's issue here - good for others to read too! There are different strategies for this but it's super important as code becomes more complex: publiclab/leaflet-environmental-layers#207

[pdurbin]

I type git status so much that I shorten it to gits with this Bash alias:

alias gits='git status'

Speaking of aliases, git itself supports them. I have a lot in my .gitconfig at https://github.com/pdurbin but I only use a couple of them regularly.

I shorten git checkout to git co.

I also like being able to specify an alternative email address after I've cloned a git repo. For example, if I want to make commits using my work email address, I cd into the repo and type git harvard.

Here's the .gitconfig file:

[user]
	name  = Philip Durbin
	email = philipdurbin@gmail.com
[alias]
	co      = checkout
	harvard = config user.email philip_durbin@harvard.edu

[divyabaid16]

Hi everyone!

Great theme @sashadev-sky 🎉

Well, I just use Bash Alias to clear my terminal xD
alias c='clear' and not for other things. For me writing the complete command is much easier.

And I guess, I just missed my previous week's check-in so I will write about my work for the past 2 weeks.

FTO's created:
publiclab/mapknitter#739
publiclab/mapknitter#722
publiclab/mapknitter#723
publiclab/mapknitter#673

PR's created (open):
publiclab/mapknitter#738
publiclab/mapknitter#693

PR's merged:
publiclab/mapknitter#735
publiclab/mapknitter#721
publiclab/mapknitter#717
publiclab/mapknitter#692
publiclab/mapknitter#689

Goals for this week:

• Get started with the image version control. Here, the details of all the edits must be available to the user and can select any version as the version to be displayed on the map.
• Get completed with multiple image export
• Find and work on other bugs.

Have a great week ahead everyone.
Thanks! :)

[jywarren]

Hi, everyone! I wrote up a post about "how to get help effectively"! It's based on some advice I put into the GSoC evals. I think it's worth a read, and would love feedback!

https://publiclab.org/notes/warren/06-27-2019/getting-help-in-a-coding-project

[SidharthBansal]

I hope you all are going good. I am right now busy with some personal stuff. Will be back after a month.
I hope all of you enjoyed phase 1 with PL community.

[alaxalves]

Hi, everyone! I wrote up a post about "how to get help effectively"! It's based on some advice I put into the GSoC evals. I think it's worth a read, and would love feedback!

https://publiclab.org/notes/warren/06-27-2019/getting-help-in-a-coding-project

Those are very good tips, despite of being kinda boring, being pretty descriptive on issues and PRs are very necessary. BTW a good practice I took from @sashadev-sky is using this section of github to review PR and such:

Very useful to exactly express what we want.

[grvsachdeva]

Hey @alaxalves, you would be opening check-in for this week, right?

[alaxalves]

@gauravano It's here guys -> publiclab/mapknitter#772