1. rm -rf .idea
2. delete these in .gitignore

/.idea/workspace.xml
/.idea/libraries
/.idea/misc.xml

3. Add this to .gitignore

.idea

Actual Behaviour

There is a lot of boilerplate code inside the POJOs.

Expected Behaviour

These can be replaced by using Lombok

Expected Behaviour

Setup UI for Attendance manager

To be treated as a parent issue.

To implement the fetching of Contest data for the coding calendar module from the Hackerrank url.

Actual Behaviour

Right now we are using Butterknife to reduce the boilerplate code for view bindings.

Expected Behaviour

The official Data binding framework is extremely powerful and supports two way data binding as well. Replace the usage of Butterknife and refactor to use the data binding library.

Now that we are going to follow MVVM architecture, we should specifically mention it in the project's README.

Expected Behaviour

Create ViewModel for Views.

Parent issue

#48

Actual Behaviour

Right now there is no support for updating a current subject details in the AttendanceManager.

Expected Behaviour

There should be support for it.

Add build status badge in readme file to show status of travis build.

Actual Behaviour

The Gradle plugin versions are outdated.

Expected Behaviour

The project should be updated to use Android studio 3.0

Would you like to work on the issue?

Yes

Actual Behaviour

There is a semester pojo inside Attendence manager.

Expected Behaviour

I feel it will only complicate things and it doesn't have any use case.
I don't think anyone would like to save his/her attendence for previous semesters.
Hence we only need to store the data for the current semester and provide option to delete the data so that the user can delete the previous semester data before start of each semester.

Would you like to work on the issue?

Yes.

Expected Behaviour

Write ViewModel tests for

• CodingCalendarViewModel
• ContestDetailViewModel

Parent issue

#48

Implement the RecyclerViewAdapter to populate the coding calendar recycler view with data.

Implement deletion of a single contest in the Database ContentProvider.

We need to pull the data back from the Winter of code repository since the Winter of Code is over.

Make database for the attendance manager.

Someone please design app icon.

The project idea was taken from an active open source project created by the students of NSIT - https://github.com/Swati4star/NSIT-Connect.

Add idea credit in the readme since it isn't our original idea.

Feature Request

Feature Description

Right now we aren't using DI. It should be introduced in the project as it allows for better decoupling.

Since there isn't a proper place to add the detailed Roadmap of the project and discuss it. I'll add it here.
Here are the next few steps that we have to take:

• Migrate to ROOM in Coding calendar (#59 )
  We cannot use two databases at the same time and it would be very time-consuming to use Content providers for other features also. So the best solution would be to refactor Coding calendar to use ROOM.

• Create the database for Attendance manager.(#15 )

• Create the UI for Attendance manager(#71 )

Will keep on adding as they come.

@mayank8318 @arundhati24

Currently we can't scroll through the entire page in some of the contest detail activities, where the title of the contest is big or the data does not fit into a single screen.

For example :

Currently the user is not allowed to refresh this page. Adding swipe to refresh will allow the user to refresh the Coding Calendar home page.

Currently all the builds are failing with the following error message :

Error: Target id is not valid. Use 'android list targets' to get the target ids.  
The command "echo no | android create avd --force -n test -t android-22 --abi armeabi-v7a" failed and exited with 1 during .  
Your build has been stopped.

Full report

Expected Behaviour

Setup POJOs for Attendence Manager

Would you like to work on the issue?

Yes,on it.

Decide here for app theme and color scheme. Please comment your ideas and finalize it ASAP.

Actual Behaviour

The app is currently written in Java.

Expected Behaviour

Kotlin bring exciting new features and hence should be used. Now is a good time since we have a small codebase right now.

Not a priority right now.

Feature Request

Feature Description

Create an application class to initialize the application.

Polish the UI for the RecyclerView.

There is no specific architechture of the application right now. We should develop new modules using MVVM architecture and refactor CodingCalendar later to MVVM.

• Create ViewModels
• Wrap data into LiveData
• Migrate to Room
• Write ViewModel tests.

Not a current priority but certainly for the future.

Actual Behaviour

Packages in the project are not in lowercase.

Expected Behaviour

They should be in lowercase.

Would you like to work on the issue?

No. Can be taken by a beginner.

Use any open API and implement coding calender. Discuss on design and implementation here.

Implementing Parceable interface on the Contest class means that the object can be transferred along side Intent. Also implement the onClickListener for the coding calendar RecyclerView.

Implement Contest details Acitivity and show the contest start time, end time , platform etc.

Make a basic UI with a recycler view and FAB.

Parent issue

#71

Add MIT license to the project. Other options available are Apache and GPL but MIT it better and suitable in my opinion. @srv-twry @mayank8318 views?

More information https://travis-ci.org/

Currently the ContestDetailsActivity just gets the job done but it looks ugly. It's UI needs a lot of polishing.

Make a card to be used for each subject in the attendance manager feature

Expected Behaviour

Migrate to ROOM from Content Providers

Parent issue

#48

Is your feature request related to a problem? Please describe.
A little bit of setup has already been done for Firebase authentication. We need to take it forwards.

Actual Behaviour

The Travis build fails after upgrading Gradle settings.

Expected Behaviour

It should be fixed ASAP

Expected Behaviour

Add feature of adding Schedule in Attendence Manager. Right now, the user has to manually mark his attendence for each subject.
Prompt the user to mark his/her attendence according to the schedule.

Create child issues if needed.

Actual Behaviour

There are a lot of formatting errors in the whole project.

Expected Behaviour

Use Android studio shortcut ctrl+alt+l to reformat the code in every file.

Actual Behaviour

Right now we are using the default logging component provided by the Android SDK.

Expected Behaviour

We should use Timber for logging because it's very popular and is the industry standard.
Refactor all logging statements(if any) to use Timber

Would you like to work on the issue?

Yes

Actual Behaviour

The package structure in the project isn't right.

Expected Behaviour

Take inspiration from one of the open source android projects and allign accordingly.

Actual Behaviour
Currently the contest title in the recycler view list item does not fit properly in the text view in landscape orientation. Also ellipsis does not appear in this case.

Screenshots for current behaviour :
Portrait orientation :

Landscape orientation :

Required behaviour

Populate the database with the fetched contest data. Implement insert,query and delete operations.